Managing data from internet of things devices in a vehicle

ABSTRACT

A method and system for communicating with IoT devices connected to a vehicle to gather information related to device operation or performance is disclosed. The system makes a copy of at least a portion of the device&#39;s non-volatile memory and/or receives IoT device data (e.g., sensor data and/or log files etc.) from an IoT device that recently failed. The system determines which log files and/or sensor data, for example, the IoT device created before and/or after a failure. After gathering this information, the system stores the information, sends it to a storage destination for further analysis and diagnostics to troubleshoot the failure and send a fix or software update to the IoT device. The information can also be placed into secondary storage to comply with regulatory, insurance, or legal purposes.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation-in-part of U.S. application Ser. No.16/875,854, filed on May 15, 2020 and a continuation-in-part of U.S.patent application Ser. No. 16/732,271, filed on Dec. 31, 2019 which isa continuation of U.S. patent application Ser. No. 15/915,000, filedMar. 7, 2018 (issued as U.S. Pat. No. 10,552,294), which claims thebenefit of U.S. Provisional Patent Application No. 62/479,755, filed onMar. 31, 2017, entitled “MANAGEMENT OF INTERNET OF THINGS DEVICES”. Anyand all applications for which a foreign or domestic priority claim isidentified in the Application Data Sheet of the present application arehereby incorporated by reference in their entireties under 37 CFR 1.57.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone, of the patentdocument and/or the patent disclosure as it appears in the United StatesPatent and Trademark Office patent file and/or records, but otherwisereserves all copyrights whatsoever.

BACKGROUND

Businesses recognize the commercial value of their data and seekreliable, cost-effective ways to protect the information stored on theircomputer networks while minimizing impact on productivity. A companymight back up critical computing systems such as databases, fileservers, web servers, virtual machines, and so on as part of a daily,weekly, or monthly maintenance schedule. The company may similarlyprotect computing systems used by its employees, such as those used byan accounting department, marketing department, engineering department,and so forth. Given the rapidly expanding volume of data undermanagement, companies also continue to seek innovative techniques formanaging data growth, for example by migrating data to lower-coststorage over time, reducing redundant data, pruning lower priority data,etc. Enterprises also increasingly view their stored data as a valuableasset and look for solutions that leverage their data. For instance,data analysis capabilities, information management, improved datapresentation and access features, and the like, are in increasingdemand.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an exemplary informationmanagement system.

FIG. 1B is a detailed view of a primary storage device, a secondarystorage device, and some examples of primary data and secondary copydata.

FIG. 1C is a block diagram of an exemplary information management systemincluding a storage manager, one or more data agents, and one or moremedia agents.

FIG. 1D is a block diagram illustrating a scalable informationmanagement system.

FIG. 1E illustrates certain secondary copy operations according to anexemplary storage policy.

FIGS. 1F-1H are block diagrams illustrating suitable data structuresthat may be employed by the information management system.

FIG. 2A illustrates a system and technique for synchronizing primarydata to a destination such as a failover site using secondary copy data.

FIG. 2B illustrates an information management system architectureincorporating use of a network file system (NFS) protocol forcommunicating between the primary and secondary storage subsystems.

FIG. 2C is a block diagram of an example of a highly scalable manageddata pool architecture.

FIG. 3 is a block diagram illustrating an environment for gathering andprotecting data for Internet of Things (IoT) devices.

FIGS. 4A and 4B are block diagrams illustrating some of the componentsfrom the environment in FIG. 3 in more detail.

FIG. 5 is a flow diagram for implementing an algorithm for transferringand protecting data gathered from an IoT device.

FIG. 6A is a block diagram illustrating an environment for gathering andprotecting data for Internet of Things (IoT) devices in vehicles.

FIG. 6B is a block diagram illustrating exemplary pathways fortransferring data from a vehicle comprising IoT devices to a storagedestination.

FIG. 6C is a block diagram illustrating one exemplary pathway fortransferring data from a vehicle comprising IoT devices to the storagedestination.

FIG. 6D is a block diagram illustrating another exemplary pathway fortransferring data from a vehicle comprising IoT devices to the storagedestination.

FIG. 6E is a block diagram illustrating another exemplary pathway fortransferring data from a vehicle comprising IoT devices to the storagedestination.

FIGS. 7A and 7B are block diagrams illustrating some of the componentsfrom the environment in FIG. 6 in more detail.

FIG. 8 is a flow diagram for implementing a process for transferring andprotecting data gathered from IoT devices inside a vehicle.

FIG. 9 is a flow diagram illustrating a process for transferring andprotecting IoT device data for a vehicle at a docking station.

DETAILED DESCRIPTION

Internet of things (IoT) devices are quickly becoming ubiquitousworldwide. By 2020, 50 million IoT devices will be connected to theInternet, and IoT manufacturers plan to spend $1 trillion USD per yearon IoT devices. IoT devices include sensors and actuators embedded inphysical objects that are linked through wired and wireless networks,often using the Internet Protocol (IP). IoT devices also use Wi-Fi,ZigBee®, Bluetooth®, and/or other protocols to connect with each otherand/or with computer devices. Well known examples of IoT devices arewearable devices such as fitness trackers, home automation devices suchas a Nest® thermostat, and industrial asset monitoring devices such asthe Family Hub® refrigerator from Samsung™. The automotive sector isalso adopting IoT devices into vehicles. For instance, IoT devices canbe found in trucks, transit buses, and tractor trailers to track fleetlocation and give management transparency on the fleet's activities.Having these IoT devices onboard trucks, for example, may also providedata on environmental conditions and cargo weight, and/or track trafficand road conditions and/or fuel expenditures, without limitation. Thiscan lead to greater cargo efficiency, improve driver safety, and reduceoverall costs associated with operating a fleet of vehicles. Even in theabsence of a fleet setting, vehicle-based IoT devices can provide awealth of information to vehicle and component manufacturers, servicepersonnel, regulators, owners, and/or users.

While these IoT devices have the potential to provide significantinformation related to operation and performance of a vehicle, some ofthese IoT devices have limited computational and software resources.These devices are also referred to as “limited resource IoT devices,”because they have less processor power and less memory compared to alaptop or desktop computer. Limited resource IoT devices also lackdiagnostic or other software that would enable an IoT device to diagnoseerrors or to communicate troubleshooting information for review to alaptop, server, network, or technician. Although manufacturers couldincrease the processor power or memory size of limited resource IoTdevices, the manufacturers generally produce these devices to keepweight, energy, and costs low; in addition, these devices have generallysimple functions (e.g., sensing information) that may not require highprocessing power or large memory. As a result of the limited hardwareand software resources, some manufacturers encounter difficulties infixing, diagnosing, or communicating with limited resource IoT devices.

Not only do limited resource IoT devices lack the requisite large memoryto store large amounts of data, but the IoT devices lack the hardware orsoftware to determine what data is related to failure or error. Forexample, a cargo monitor in a truck can produce terabytes of datarelated to operating conditions such as weight of the cargo,temperature, run time, and power used over a few months. However, suchmonitors generally do not store all of this information because a largeamount of this data may be related to normal operation of the IoTdevice, and the devices lack the intelligence to sort through andcategorize data as error- or failure-related. In addition, manufacturersmay be generally more interested in data that corresponds to an error orfailure with the device than normal operation of the device.Accordingly, there exists a need for a technology that addresses theseshortcomings.

In contrast to traditional IoT technology discussed above, the disclosedtechnology communicates with IoT devices in vehicles to gatherinformation related to operation or performance of the device even ifthe IoT devices are limited in resources. For example, the disclosedtechnology can receive data such as log files from a vehicle containingIoT devices. The disclosed technology can identify the data createdbefore and/or after a failure. After the disclosed technology gathersthis information, it can store the information in a database, send it toa cloud storage environment accessible by IoT device-related entities(e.g., IoT device manufacturers), and the device-related entity usesthis information to troubleshoot the failure and send a fix or softwareupdate to the IoT device. In some embodiments, the information gatheredis not limited to device failures and errors and can be any datagenerated and/or stored at or by the IoT device. In any of theseembodiments, the gathered information is then protected for the longerterm by an illustrative information management system.

In one exemplary embodiment, a system for protecting IoT (internet ofthings) device data connected to a vehicle is disclosed. The systemcommunicates with the IoT devices to collect data on the operation andperformance of the IoT devices that are connected to the vehicle. Thesystem may be composed of at least one IoT (internet of things) devicehaving a processor and nonvolatile memory and an IoT monitor incommunication with the at least one IoT device. The IoT devices maygenerate data (e.g., based on a triggering event) that may be collectedand stored at such time when the data can be transmitted across anetwork to a destination storage environment such as a cloud storage oran information management system. The system may or may not utilize anintermediate vehicle docking station to facilitate transmission of thedata. More specifically, IoT data agents, whose functionalities may bedistributed among the IoT devices, the IoT monitor, the docking station,or the information management, perform certain information managementoperations of the IoT device data such as copying, archiving, migrating,and/or replicating, without limitation. Thus, the illustrative systemhas features for capturing IoT-generated data, including from vehicles,and protects this data in storage resources apart from the IoT devicesand their host vehicles.

In another exemplary embodiment, a computer-implemented method to managedata from IoT devices connected to a vehicle is disclosed. The IoTdevice generates IoT device data such as log files associated with theoperation or performance of the IoT device in the vehicle. The methodestablishes, by an IoT monitor connected to the IoT devices, that atriggering event has occurred. The triggering event can be based on apredetermined storage policy, an error, a failure, or a malfunction ofan IoT device connected to the vehicle. The IoT monitor can poll the IoTdevices for triggering events. An IoT data agent associated with the IoTdevice or IoT monitor running on the vehicle may take a snapshot of theIoT device memory or make a replica of the IoT device memoryexperiencing the triggering event. The snapshot, replica, or log files(i.e., IoT device data) may be stored in a database until a connectionis made by the vehicle with a docking station that is connected, througha network, to either a cloud storage or an information managementsystem. In other embodiments, the IoT data agent or IoT monitor may notbe located on the vehicle. In such embodiments, the IoT data agent orIoT monitor may be located in a device outside of the vehicle. In suchcases, snapshots can be made or replicas can be taken when the vehicleis connected to such devices (e.g., docking station or some othercommunicative coupling) having the IoT data agent or IoT monitorfunctionalities. The collected IoT device data may be transferredthrough the network to the cloud storage or the information managementsystem for analysis and testing, software fixes, for archiving to meetregulatory or compliance requirements, or integrated into an analyticsengine to provide further insight into the IoT device data.

In yet another exemplary embodiment, a computer-implemented method tomanage data from IoT devices connected to a vehicle is furtherdisclosed. The method connects a vehicle containing IoT devices thatassist with the operation or performance of the vehicle to a vehicledocking station. These IoT devices having a processor and non-volatilememory may generate IoT device data related to the operation orfunctioning of the devices in the vehicle. Upon a triggering event, IoTdevice data or a portion thereof can be captured and sent to a remotestorage location such as a cloud storage environment. When the vehicleis docked at the docking station, an IoT data agent can authenticate thevehicle and its component IoT devices and determine that a triggeringevent has occurred with the IoT devices. The IoT data agent can retrievethe previously stored IoT device data from the cloud storage andassociate the previously stored IoT device data with the IoT device datareceived from the vehicle. The associated data can then be sent to theinformation management system for storage, testing, and analysis aspreviously described.

Detailed descriptions and examples of systems and methods according toone or more illustrative embodiments of the present invention may befound in the section titled Management of Internet of Things (IoT)Devices in Vehicles, and also in FIGS. 6-9 herein. Furthermore,components and functionality for management of IoT devices may beconfigured and/or incorporated into information management systems suchas those described herein in FIGS. 1A-1H and 2A-2C, as well as in FIGS.3-5 herein.

Various implementations described herein are intimately tied to, enabledby, and would not exist except for, computer technology. For example, asystem for managing IoT devices, tracking errors of IoT devices,transferring data from an IoT device to a database or from one databaseto another remote database, or system for improving the operation of IoTdevices by monitoring the devices for errors cannot reasonably beperformed by humans alone, without the computer technology upon whichthey are implemented. Additionally, it is not possible for humans fordetermine the errors associated with many IoT devices spread across anetwork, where the IoT devices can have different hardware, software,and protocols.

A. Information Management System Overview

With the increasing importance of protecting and leveraging data,organizations simply cannot risk losing critical data. Moreover, runawaydata growth and other modern realities make protecting and managing dataincreasingly difficult. There is therefore a need for efficient,powerful, and user-friendly solutions for protecting and managing dataand for smart and efficient management of data storage. Depending on thesize of the organization, there may be many data production sourceswhich are under the purview of tens, hundreds, or even thousands ofindividuals. In the past, individuals were sometimes responsible formanaging and protecting their own data, and a patchwork of hardware andsoftware point solutions may have been used in any given organization.These solutions were often provided by different vendors and had limitedor no interoperability. Certain embodiments described herein addressthese and other shortcomings of prior approaches by implementingscalable, unified, organization-wide information management, includingdata storage management.

FIG. 1A shows one such information management system 100 (or “system100”), which generally includes combinations of hardware and softwareconfigured to protect and manage data and metadata that are generatedand used by computing devices in system 100. System 100 may be referredto in some embodiments as a “storage management system” or a “datastorage management system.” System 100 performs information managementoperations, some of which may be referred to as “storage operations” or“data storage operations,” to protect and manage the data residing inand/or managed by system 100. The organization that employs system 100may be a corporation or other business entity, non-profit organization,educational institution, household, governmental agency, or the like.

Generally, the systems and associated components described herein may becompatible with and/or provide some or all of the functionality of thesystems and corresponding components described in one or more of thefollowing U.S. patents/publications and patent applications assigned toCommvault Systems, Inc., each of which is hereby incorporated byreference in its entirety herein:

-   -   U.S. Pat. No. 7,035,880, entitled “Modular Backup and Retrieval        System Used in Conjunction With a Storage Area Network”;    -   U.S. Pat. No. 7,107,298, entitled “System And Method For        Archiving Objects In An Information Store”;    -   U.S. Pat. No. 7,246,207, entitled “System and Method for        Dynamically Performing Storage Operations in a Computer        Network”;    -   U.S. Pat. No. 7,315,923, entitled “System And Method For        Combining Data Streams In Pipelined Storage Operations In A        Storage Network”;    -   U.S. Pat. No. 7,343,453, entitled “Hierarchical Systems and        Methods for Providing a Unified View of Storage Information”;    -   U.S. Pat. No. 7,395,282, entitled “Hierarchical Backup and        Retrieval System”;    -   U.S. Pat. No. 7,529,782, entitled “System and Methods for        Performing a Snapshot and for Restoring Data”;    -   U.S. Pat. No. 7,617,262, entitled “System and Methods for        Monitoring Application Data in a Data Replication System”;    -   U.S. Pat. No. 7,734,669, entitled “Managing Copies Of Data”;    -   U.S. Pat. No. 7,747,579, entitled “Metabase for Facilitating        Data Classification”;    -   U.S. Pat. No. 8,156,086, entitled “Systems And Methods For        Stored Data Verification”;    -   U.S. Pat. No. 8,170,995, entitled “Method and System for Offline        Indexing of Content and Classifying Stored Data”;    -   U.S. Pat. No. 8,230,195, entitled “System And Method For        Performing Auxiliary Storage Operations”;    -   U.S. Pat. No. 8,285,681, entitled “Data Object Store and Server        for a Cloud Storage Environment, Including Data Deduplication        and Data Management Across Multiple Cloud Storage Sites”;    -   U.S. Pat. No. 8,307,177, entitled “Systems And Methods For        Management Of Virtualization Data”;    -   U.S. Pat. No. 8,364,652, entitled “Content-Aligned, Block-Based        Deduplication”;    -   U.S. Pat. No. 8,578,120, entitled “Block-Level Single        Instancing”;    -   U.S. Pat. No. 8,954,446, entitled “Client-Side Repository in a        Networked Deduplicated Storage System”;    -   U.S. Pat. No. 9,020,900, entitled “Distributed Deduplicated        Storage System”;    -   U.S. Pat. No. 9,098,495, entitled “Application-Aware and Remote        Single Instance Data Management”;    -   U.S. Pat. No. 9,239,687, entitled “Systems and Methods for        Retaining and Using Data Block Signatures in Data Protection        Operations”;    -   U.S. Pat. Pub. No. 2006/0224846, entitled “System and Method to        Support Single Instance Storage Operations”;    -   U.S. Pat. Pub. No. 2014/0201170, entitled “High Availability        Distributed Deduplicated Storage System”, now U.S. Pat. No.        9,633,033;    -   U.S. Pat. Pub. No. 2016/0041880 A1, entitled “Efficient        Application Recovery in an Information Management System Based        on a Pseudo-Storage-Device Driver”, now U.S. Pat. No. 9,852,026;    -   U.S. patent application Ser. No. 14/721,971, entitled        “Replication Using Deduplicated Secondary Copy Data”, published        as U.S. Pat. Pub. No. 2016/0350391;    -   U.S. patent application Ser. No. 14/805,615, entitled “Browse        and Restore for Block-Level Backups”, now U.S. Pat. No.        9,766,825.    -   U.S. Provisional Patent Application No. 62/265,339 entitled        “Live Synchronization and Management of Virtual Machines across        Computing and Virtualization Platforms and Using Live        Synchronization to Support Disaster Recovery”, to which U.S.        patent application Ser. No. 15/365,756 claims priority (now U.S.        Pat. No. 10,228,962);    -   U.S. Provisional Patent Application No. 62/273,286 entitled        “Redundant and Robust Distributed Deduplication Data Storage        System”, to which U.S. patent application Ser. No. 15/299,254        (now U.S. Pat. No. 10,310,953), Ser. No. 15/299,281 (published        as U.S. Pat Pub. 2017-0192868), Ser. No. 15/299,291 (now U.S.        Pat. No. 10,138,729), Ser. No. 15/299,298 (now U.S. Pat. No.        10,592,357), Ser. No. 15/299,299 (published as U.S. Pat. Pub. US        2017-0193003), and Ser. No. 15/299,280 (now U.S. Pat. No.        10,061,663) all claim priority;    -   U.S. Provisional Patent Application No. 62/294,920, entitled        “Data Protection Operations Based on Network Path Information”,        to which U.S. patent application Ser. No. 15/283,033 claims        priority (published as U.S. Pat. Pub. No. 2017/0235647;    -   U.S. Provisional Patent Application No. 62/297,057, entitled        “Data Restoration Operations Based on Network Path Information”,        to which U.S. patent application Ser. No. 15/286,403 claims        priority (published as U.S. Pat. Pub. No. 2017/0242871); and    -   U.S. Provisional Patent Application No. 62/387,384, entitled        “Application-Level Live Synchronization Across Computing        Platforms Including Synchronizing Co-Resident Applications To        Disparate Standby Destinations And Selectively Synchronizing        Some Applications And Not Others”, to which U.S. patent        application Ser. No. 15/369,676 claims priority (now U.S. Pat.        No. 10,387,266).

System 100 includes computing devices and computing technologies. Forinstance, system 100 can include one or more client computing devices102 and secondary storage computing devices 106, as well as storagemanager 140 or a host computing device for it. Computing devices caninclude, without limitation, one or more: workstations, personalcomputers, desktop computers, or other types of generally fixedcomputing systems such as mainframe computers, servers, andminicomputers. Other computing devices can include mobile or portablecomputing devices, such as one or more laptops, tablet computers,personal data assistants, mobile phones (such as smartphones), and othermobile or portable computing devices such as embedded computers, set topboxes, vehicle-mounted devices, wearable computers, etc. Servers caninclude mail servers, file servers, database servers, virtual machineservers, and web servers. Any given computing device comprises one ormore processors (e.g., CPU and/or single-core or multi-core processors),as well as corresponding non-transitory computer memory (e.g.,random-access memory (RAM)) for storing computer programs which are tobe executed by the one or more processors. Other computer memory formass storage of data may be packaged/configured with the computingdevice (e.g., an internal hard disk) and/or may be external andaccessible by the computing device (e.g., network-attached storage, astorage array, etc.). In some cases, a computing device includes cloudcomputing resources, which may be implemented as virtual machines. Forinstance, one or more virtual machines may be provided to theorganization by a third-party cloud service vendor.

In some embodiments, computing devices can include one or more virtualmachine(s) running on a physical host computing device (or “hostmachine”) operated by the organization. As one example, the organizationmay use one virtual machine as a database server and another virtualmachine as a mail server, both virtual machines operating on the samehost machine. A Virtual machine (“VM”) is a software implementation of acomputer that does not physically exist and is instead instantiated inan operating system of a physical computer (or host machine) to enableapplications to execute within the VM's environment, i.e., a VM emulatesa physical computer. A VM includes an operating system and associatedvirtual resources, such as computer memory and processor(s). Ahypervisor operates between the VM and the hardware of the physical hostmachine and is generally responsible for creating and running the VMs.Hypervisors are also known in the art as virtual machine monitors or avirtual machine managers or “VMMs”, and may be implemented in software,firmware, and/or specialized hardware installed on the host machine.Examples of hypervisors include ESX Server, by VMware, Inc. of PaloAlto, Calif.; Microsoft Virtual Server and Microsoft Windows ServerHyper-V, both by Microsoft Corporation of Redmond, Wash.; Sun xVM byOracle America Inc. of Santa Clara, Calif.; and Xen by Citrix Systems,Santa Clara, Calif. The hypervisor provides resources to each virtualoperating system such as a virtual processor, virtual memory, a virtualnetwork device, and a virtual disk. Each virtual machine has one or moreassociated virtual disks. The hypervisor typically stores the data ofvirtual disks in files on the file system of the physical host machine,called virtual machine disk files (“VMDK” in VMware lingo) or virtualhard disk image files (in Microsoft lingo). For example, VMware's ESXServer provides the Virtual Machine File System (VMFS) for the storageof virtual machine disk files. A virtual machine reads data from andwrites data to its virtual disk much the way that a physical machinereads data from and writes data to a physical disk. Examples oftechniques for implementing information management in a cloud computingenvironment are described in U.S. Pat. No. 8,285,681. Examples oftechniques for implementing information management in a virtualizedcomputing environment are described in U.S. Pat. No. 8,307,177.

Information management system 100 can also include electronic datastorage devices, generally used for mass storage of data, including,e.g., primary storage devices 104 and secondary storage devices 108.Storage devices can generally be of any suitable type including, withoutlimitation, disk drives, storage arrays (e.g., storage-area network(SAN) and/or network-attached storage (NAS) technology), semiconductormemory (e.g., solid state storage devices), network attached storage(NAS) devices, tape libraries, or other magnetic, non-tape storagedevices, optical media storage devices, DNA/RNA-based memory technology,combinations of the same, etc. In some embodiments, storage devices formpart of a distributed file system. In some cases, storage devices areprovided in a cloud storage environment (e.g., a private cloud or oneoperated by a third-party vendor), whether for primary data or secondarycopies or both.

Depending on context, the term “information management system” can referto generally all of the illustrated hardware and software components inFIG. 1C, or the term may refer to only a subset of the illustratedcomponents. For instance, in some cases, system 100 generally refers toa combination of specialized components used to protect, move, manage,manipulate, analyze, and/or process data and metadata generated byclient computing devices 102. However, system 100 in some cases does notinclude the underlying components that generate and/or store primarydata 112, such as the client computing devices 102 themselves, and theprimary storage devices 104. Likewise secondary storage devices 108(e.g., a third-party provided cloud storage environment) may not be partof system 100. As an example, “information management system” or“storage management system” may sometimes refer to one or more of thefollowing components, which will be described in further detail below:storage manager, data agent, and media agent.

One or more client computing devices 102 may be part of system 100, eachclient computing device 102 having an operating system and at least oneapplication 110 and one or more accompanying data agents executingthereon; and associated with one or more primary storage devices 104storing primary data 112. Client computing device(s) 102 and primarystorage devices 104 may generally be referred to in some cases asprimary storage subsystem 117.

B. Client Computing Devices, Clients, and Subclients

Typically, a variety of sources in an organization produce data to beprotected and managed. As just one illustrative example, in a corporateenvironment such data sources can be employee workstations and companyservers such as a mail server, a web server, a database server, atransaction server, or the like. In system 100, data generation sourcesinclude one or more client computing devices 102. A computing devicethat has a data agent 142 installed and operating on it is generallyreferred to as a “client computing device” 102, and may include any typeof computing device, without limitation. A client computing device 102may be associated with one or more users and/or user accounts.

A “client” is a logical component of information management system 100,which may represent a logical grouping of one or more data agentsinstalled on a client computing device 102. Storage manager 140recognizes a client as a component of system 100, and in someembodiments, may automatically create a client component the first timea data agent 142 is installed on a client computing device 102. Becausedata generated by executable component(s) 110 is tracked by theassociated data agent 142 so that it may be properly protected in system100, a client may be said to generate data and to store the generateddata to primary storage, such as primary storage device 104. However,the terms “client” and “client computing device” as used herein do notimply that a client computing device 102 is necessarily configured inthe client/server sense relative to another computing device such as amail server, or that a client computing device 102 cannot be a server inits own right. As just a few examples, a client computing device 102 canbe and/or include mail servers, file servers, database servers, virtualmachine servers, and/or web servers.

Each client computing device 102 may have application(s) 110 executingthereon which generate and manipulate the data that is to be protectedfrom loss and managed in system 100. Applications 110 generallyfacilitate the operations of an organization, and can include, withoutlimitation, mail server applications (e.g., Microsoft Exchange Server),file system applications, mail client applications (e.g., MicrosoftExchange Client), database applications or database management systems(e.g., SQL, Oracle, SAP, Lotus Notes Database), word processingapplications (e.g., Microsoft Word), spreadsheet applications, financialapplications, presentation applications, graphics and/or videoapplications, browser applications, mobile applications, entertainmentapplications, and so on. Each application 110 may be accompanied by anapplication-specific data agent 142, though not all data agents 142 areapplication-specific or associated with only application. A file system,e.g., Microsoft Windows Explorer, may be considered an application 110and may be accompanied by its own data agent 142. Client computingdevices 102 can have at least one operating system (e.g., MicrosoftWindows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-based operatingsystems, etc.) installed thereon, which may support or host one or morefile systems and other applications 110. In some embodiments, a virtualmachine that executes on a host client computing device 102 may beconsidered an application 110 and may be accompanied by a specific dataagent 142 (e.g., virtual server data agent).

Client computing devices 102 and other components in system 100 can beconnected to one another via one or more electronic communicationpathways 114. For example, a first communication pathway 114 maycommunicatively couple client computing device 102 and secondary storagecomputing device 106; a second communication pathway 114 maycommunicatively couple storage manager 140 and client computing device102; and a third communication pathway 114 may communicatively couplestorage manager 140 and secondary storage computing device 106, etc.(see, e.g., FIG. 1A and FIG. 1C). A communication pathway 114 caninclude one or more networks or other connection types including one ormore of the following, without limitation: the Internet, a wide areanetwork (WAN), a local area network (LAN), a Storage Area Network (SAN),a Fibre Channel (FC) connection, a Small Computer System Interface(SCSI) connection, a virtual private network (VPN), a token ring orTCP/IP based network, an intranet network, a point-to-point link, acellular network, a wireless data transmission system, a two-way cablesystem, an interactive kiosk network, a satellite network, a broadbandnetwork, a baseband network, a neural network, a mesh network, an ad hocnetwork, other appropriate computer or telecommunications networks,combinations of the same or the like. Communication pathways 114 in somecases may also include application programming interfaces (APIs)including, e.g., cloud service provider APIs, virtual machine managementAPIs, and hosted service provider APIs. The underlying infrastructure ofcommunication pathways 114 may be wired and/or wireless, analog and/ordigital, or any combination thereof; and the facilities used may beprivate, public, third-party provided, or any combination thereof,without limitation.

A “subclient” is a logical grouping of all or part of a client's primarydata 112. In general, a subclient may be defined according to how thesubclient data is to be protected as a unit in system 100. For example,a subclient may be associated with a certain storage policy. A givenclient may thus comprise several subclients, each subclient associatedwith a different storage policy. For example, some files may form afirst subclient that requires compression and deduplication and isassociated with a first storage policy. Other files of the client mayform a second subclient that requires a different retention schedule aswell as encryption, and may be associated with a different, secondstorage policy. As a result, though the primary data may be generated bythe same application 110 and may belong to one given client, portions ofthe data may be assigned to different subclients for distinct treatmentby system 100. More detail on subclients is given in regard to storagepolicies below.

C. Primary Data and Exemplary Primary Storage Devices

Primary data 112 is generally production data or “live” data generatedby the operating system and/or applications 110 executing on clientcomputing device 102. Primary data 112 is generally stored on primarystorage device(s) 104 and is organized via a file system operating onthe client computing device 102. Thus, client computing device(s) 102and corresponding applications 110 may create, access, modify, write,delete, and otherwise use primary data 112. Primary data 112 isgenerally in the native format of the source application 110. Primarydata 112 is an initial or first stored body of data generated by thesource application 110. Primary data 112 in some cases is createdsubstantially directly from data generated by the corresponding sourceapplication 110. It can be useful in performing certain tasks toorganize primary data 112 into units of different granularities. Ingeneral, primary data 112 can include files, directories, file systemvolumes, data blocks, extents, or any other hierarchies or organizationsof data objects. As used herein, a “data object” can refer to (i) anyfile that is currently addressable by a file system or that waspreviously addressable by the file system (e.g., an archive file),and/or to (ii) a subset of such a file (e.g., a data block, an extent,etc.). Primary data 112 may include structured data (e.g., databasefiles), unstructured data (e.g., documents), and/or semi-structureddata. See, e.g., FIG. 1B.

It can also be useful in performing certain functions of system 100 toaccess and modify metadata within primary data 112. Metadata generallyincludes information about data objects and/or characteristicsassociated with the data objects. For simplicity herein, it is to beunderstood that, unless expressly stated otherwise, any reference toprimary data 112 generally also includes its associated metadata, butreferences to metadata generally do not include the primary data.Metadata can include, without limitation, one or more of the following:the data owner (e.g., the client or user that generates the data), thelast modified time (e.g., the time of the most recent modification ofthe data object), a data object name (e.g., a file name), a data objectsize (e.g., a number of bytes of data), information about the content(e.g., an indication as to the existence of a particular search term),user-supplied tags, to/from information for email (e.g., an emailsender, recipient, etc.), creation date, file type (e.g., format orapplication type), last accessed time, application type (e.g., type ofapplication that generated the data object), location/network (e.g., acurrent, past or future location of the data object and network pathwaysto/from the data object), geographic location (e.g., GPS coordinates),frequency of change (e.g., a period in which the data object ismodified), business unit (e.g., a group or department that generates,manages or is otherwise associated with the data object), aginginformation (e.g., a schedule, such as a time period, in which the dataobject is migrated to secondary or long term storage), boot sectors,partition layouts, file location within a file folder directorystructure, user permissions, owners, groups, access control lists(ACLs), system metadata (e.g., registry information), combinations ofthe same or other similar information related to the data object. Inaddition to metadata generated by or related to file systems andoperating systems, some applications 110 and/or other components ofsystem 100 maintain indices of metadata for data objects, e.g., metadataassociated with individual email messages. The use of metadata toperform classification and other functions is described in greaterdetail below.

Primary storage devices 104 storing primary data 112 may be relativelyfast and/or expensive technology (e.g., flash storage, a disk drive, ahard-disk storage array, solid state memory, etc.), typically to supporthigh-performance live production environments. Primary data 112 may behighly changeable and/or may be intended for relatively short termretention (e.g., hours, days, or weeks). According to some embodiments,client computing device 102 can access primary data 112 stored inprimary storage device 104 by making conventional file system calls viathe operating system. Each client computing device 102 is generallyassociated with and/or in communication with one or more primary storagedevices 104 storing corresponding primary data 112. A client computingdevice 102 is said to be associated with or in communication with aparticular primary storage device 104 if it is capable of one or moreof: routing and/or storing data (e.g., primary data 112) to the primarystorage device 104, coordinating the routing and/or storing of data tothe primary storage device 104, retrieving data from the primary storagedevice 104, coordinating the retrieval of data from the primary storagedevice 104, and modifying and/or deleting data in the primary storagedevice 104. Thus, a client computing device 102 may be said to accessdata stored in an associated storage device 104.

Primary storage device 104 may be dedicated or shared. In some cases,each primary storage device 104 is dedicated to an associated clientcomputing device 102, e.g., a local disk drive. In other cases, one ormore primary storage devices 104 can be shared by multiple clientcomputing devices 102, e.g., via a local network, in a cloud storageimplementation, etc. As one example, primary storage device 104 can be astorage array shared by a group of client computing devices 102, such asEMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV,NetApp FAS, HP EVA, and HP 3PAR.

System 100 may also include hosted services (not shown), which may behosted in some cases by an entity other than the organization thatemploys the other components of system 100. For instance, the hostedservices may be provided by online service providers. Such serviceproviders can provide social networking services, hosted email services,or hosted productivity applications or other hosted applications such assoftware-as-a-service (SaaS), platform-as-a-service (PaaS), applicationservice providers (ASPs), cloud services, or other mechanisms fordelivering functionality via a network. As it services users, eachhosted service may generate additional data and metadata, which may bemanaged by system 100, e.g., as primary data 112. In some cases, thehosted services may be accessed using one of the applications 110. As anexample, a hosted mail service may be accessed via browser running on aclient computing device 102.

D. Secondary Copies and Exemplary Secondary Storage Devices

Primary data 112 stored on primary storage devices 104 may becompromised in some cases, such as when an employee deliberately oraccidentally deletes or overwrites primary data 112. Or primary storagedevices 104 can be damaged, lost, or otherwise corrupted. For recoveryand/or regulatory compliance purposes, it is therefore useful togenerate and maintain copies of primary data 112. Accordingly, system100 includes one or more secondary storage computing devices 106 and oneor more secondary storage devices 108 configured to create and store oneor more secondary copies 116 of primary data 112 including itsassociated metadata. The secondary storage computing devices 106 and thesecondary storage devices 108 may be referred to as secondary storagesubsystem 118.

Secondary copies 116 can help in search and analysis efforts and meetother information management goals as well, such as: restoring dataand/or metadata if an original version is lost (e.g., by deletion,corruption, or disaster); allowing point-in-time recovery; complyingwith regulatory data retention and electronic discovery (e-discovery)requirements; reducing utilized storage capacity in the productionsystem and/or in secondary storage; facilitating organization and searchof data; improving user access to data files across multiple computingdevices and/or hosted services; and implementing data retention andpruning policies.

A secondary copy 116 can comprise a separate stored copy of data that isderived from one or more earlier-created stored copies (e.g., derivedfrom primary data 112 or from another secondary copy 116). Secondarycopies 116 can include point-in-time data, and may be intended forrelatively long-term retention before some or all of the data is movedto other storage or discarded. In some cases, a secondary copy 116 maybe in a different storage device than other previously stored copies;and/or may be remote from other previously stored copies. Secondarycopies 116 can be stored in the same storage device as primary data 112.For example, a disk array capable of performing hardware snapshotsstores primary data 112 and creates and stores hardware snapshots of theprimary data 112 as secondary copies 116. Secondary copies 116 may bestored in relatively slow and/or lower cost storage (e.g., magnetictape). A secondary copy 116 may be stored in a backup or archive format,or in some other format different from the native source applicationformat or other format of primary data 112.

Secondary storage computing devices 106 may index secondary copies 116(e.g., using a media agent 144), enabling users to browse and restoreata later time and further enabling the lifecycle management of theindexed data. After creation of a secondary copy 116 that representscertain primary data 112, a pointer or other location indicia (e.g., astub) may be placed in primary data 112, or be otherwise associated withprimary data 112, to indicate the current location of a particularsecondary copy 116. Since an instance of a data object or metadata inprimary data 112 may change over time as it is modified by application110 (or hosted service or the operating system), system 100 may createand manage multiple secondary copies 116 of a particular data object ormetadata, each copy representing the state of the data object in primarydata 112 at a particular point in time. Moreover, since an instance of adata object in primary data 112 may eventually be deleted from primarystorage device 104 and the file system, system 100 may continue tomanage point-in-time representations of that data object, even thoughthe instance in primary data 112 no longer exists. For virtual machines,the operating system and other applications 110 of client computingdevice(s) 102 may execute within or under the management ofvirtualization software (e.g., a VMM), and the primary storage device(s)104 may comprise a virtual disk created on a physical storage device.System 100 may create secondary copies 116 of the files or other dataobjects in a virtual disk file and/or secondary copies 116 of the entirevirtual disk file itself (e.g., of an entire .vmdk file).

Secondary copies 116 are distinguishable from corresponding primary data112. First, secondary copies 116 can be stored in a different formatfrom primary data 112 (e.g., backup, archive, or other non-nativeformat). For this or other reasons, secondary copies 116 may not bedirectly usable by applications 110 or client computing device 102(e.g., via standard system calls or otherwise) without modification,processing, or other intervention by system 100 which may be referred toas “restore” operations. Secondary copies 116 may have been processed bydata agent 142 and/or media agent 144 in the course of being created(e.g., compression, deduplication, encryption, integrity markers,indexing, formatting, application-aware metadata, etc.), and thussecondary copy 116 may represent source primary data 112 withoutnecessarily being exactly identical to the source.

Second, secondary copies 116 may be stored on a secondary storage device108 that is inaccessible to application 110 running on client computingdevice 102 and/or hosted service. Some secondary copies 116 may be“offline copies,” in that they are not readily available (e.g., notmounted to tape or disk). Offline copies can include copies of data thatsystem 100 can access without human intervention (e.g., tapes within anautomated tape library, but not yet mounted in a drive), and copies thatthe system 100 can access only with some human intervention (e.g., tapeslocated at an offsite storage site).

E. Using Intermediate Devices for Creating Secondary Copies—SecondaryStorage Computing Devices

Creating secondary copies can be challenging when hundreds or thousandsof client computing devices 102 continually generate large volumes ofprimary data 112 to be protected. Also, there can be significantoverhead involved in the creation of secondary copies 116. Moreover,specialized programmed intelligence and/or hardware capability isgenerally needed for accessing and interacting with secondary storagedevices 108. Client computing devices 102 may interact directly with asecondary storage device 108 to create secondary copies 116, but in viewof the factors described above, this approach can negatively impact theability of client computing device 102 to serve/service application 110and produce primary data 112. Further, any given client computing device102 may not be optimized for interaction with certain secondary storagedevices 108.

Thus, system 100 may include one or more software and/or hardwarecomponents which generally act as intermediaries between clientcomputing devices 102 (that generate primary data 112) and secondarystorage devices 108 (that store secondary copies 116). In addition tooff-loading certain responsibilities from client computing devices 102,these intermediate components provide other benefits. For instance, asdiscussed further below with respect to FIG. 1D, distributing some ofthe work involved in creating secondary copies 116 can enhancescalability and improve system performance. For instance, usingspecialized secondary storage computing devices 106 and media agents 144for interfacing with secondary storage devices 108 and/or for performingcertain data processing operations can greatly improve the speed withwhich system 100 performs information management operations and can alsoimprove the capacity of the system to handle large numbers of suchoperations, while reducing the computational load on the productionenvironment of client computing devices 102. The intermediate componentscan include one or more secondary storage computing devices 106 as shownin FIG. 1A and/or one or more media agents 144. Media agents arediscussed further below (e.g., with respect to FIGS. 1C-1E). Thesespecial-purpose components of system 100 comprise specialized programmedintelligence and/or hardware capability for writing to, reading from,instructing, communicating with, or otherwise interacting with secondarystorage devices 108.

Secondary storage computing device(s) 106 can comprise any of thecomputing devices described above, without limitation. In some cases,secondary storage computing device(s) 106 also include specializedhardware componentry and/or software intelligence (e.g., specializedinterfaces) for interacting with certain secondary storage device(s) 108with which they may be specially associated.

To create a secondary copy 116 involving the copying of data fromprimary storage subsystem 117 to secondary storage subsystem 118, clientcomputing device 102 may communicate the primary data 112 to be copied(or a processed version thereof generated by a data agent 142) to thedesignated secondary storage computing device 106, via a communicationpathway 114. Secondary storage computing device 106 in turn may furtherprocess and convey the data or a processed version thereof to secondarystorage device 108. One or more secondary copies 116 may be created fromexisting secondary copies 116, such as in the case of an auxiliary copyoperation, described further below.

F. Exemplary Primary Data and an Exemplary Secondary Copy

FIG. 1B is a detailed view of some specific examples of primary datastored on primary storage device(s) 104 and secondary copy data storedon secondary storage device(s) 108, with other components of the systemremoved for the purposes of illustration. Stored on primary storagedevice(s) 104 are primary data 112 objects including word processingdocuments 119A-B, spreadsheets 120, presentation documents 122, videofiles 124, image files 126, email mailboxes 128 (and corresponding emailmessages 129A-C), HTML/XML or other types of markup language files 130,databases 132 and corresponding tables or other data structures133A-133C. Some or all primary data 112 objects are associated withcorresponding metadata (e.g., “Meta1-11”), which may include file systemmetadata and/or application-specific metadata. Stored on the secondarystorage device(s) 108 are secondary copy 116 data objects 134A-C whichmay include copies of or may otherwise represent corresponding primarydata 112.

Secondary copy data objects 134A-C can individually represent more thanone primary data object. For example, secondary copy data object 134Arepresents three separate primary data objects 133C, 122, and 129C(represented as 133C′, 122′, and 129C′, respectively, and accompanied bycorresponding metadata Meta11, Meta3, and Meta8, respectively).Moreover, as indicated by the prime mark (′), secondary storagecomputing devices 106 or other components in secondary storage subsystem118 may process the data received from primary storage subsystem 117 andstore a secondary copy including a transformed and/or supplementedrepresentation of a primary data object and/or metadata that isdifferent from the original format, e.g., in a compressed, encrypted,deduplicated, or other modified format. For instance, secondary storagecomputing devices 106 can generate new metadata or other informationbased on said processing, and store the newly generated informationalong with the secondary copies. Secondary copy data object 134Brepresents primary data objects 120, 133B, and 119A as 120′, 133B′, and119A′, respectively, accompanied by corresponding metadata Meta2,Meta10, and Meta1, respectively. Also, secondary copy data object 134Crepresents primary data objects 133A, 119B, and 129A as 133A′, 119B′,and 129A′, respectively, accompanied by corresponding metadata Meta9,Meta5, and Meta6, respectively.

G. Exemplary Information Management System Architecture

System 100 can incorporate a variety of different hardware and softwarecomponents, which can in turn be organized with respect to one anotherin many different configurations, depending on the embodiment. There arecritical design choices involved in specifying the functionalresponsibilities of the components and the role of each component insystem 100. Such design choices can impact how system 100 performs andadapts to data growth and other changing circumstances. FIG. 1C shows asystem 100 designed according to these considerations and includes:storage manager 140, one or more data agents 142 executing on clientcomputing device(s) 102 and configured to process primary data 112, andone or more media agents 144 executing on one or more secondary storagecomputing devices 106 for performing tasks involving secondary storagedevices 108.

1. Storage Manager

Storage manager 140 is a centralized storage and/or information managerthat is configured to perform certain control functions and also tostore certain critical information about system 100—hence storagemanager 140 is said to manage system 100. As noted, the number ofcomponents in system 100 and the amount of data under management can belarge. Managing the components and data is therefore a significant task,which can grow unpredictably as the number of components and data scaleto meet the needs of the organization. For these and other reasons,according to certain embodiments, responsibility for controlling system100, or at least a significant portion of that responsibility, isallocated to storage manager 140. Storage manager 140 can be adaptedindependently according to changing circumstances, without having toreplace or re-design the remainder of the system. Moreover, a computingdevice for hosting and/or operating as storage manager 140 can beselected to best suit the functions and networking needs of storagemanager 140. These and other advantages are described in further detailbelow and with respect to FIG. 1D.

Storage manager 140 may be a software module or other application hostedby a suitable computing device. In some embodiments, storage manager 140is itself a computing device that performs the functions describedherein. Storage manager 140 comprises or operates in conjunction withone or more associated data structures such as a dedicated database(e.g., management database 146), depending on the configuration. Thestorage manager 140 generally initiates, performs, coordinates, and/orcontrols storage and other information management operations performedby system 100, e.g., to protect and control primary data 112 andsecondary copies 116. In general, storage manager 140 is said to managesystem 100, which includes communicating with, instructing, andcontrolling in some circumstances components such as data agents 142 andmedia agents 144, etc.

As shown by the dashed arrowed lines 114 in FIG. 1C, storage manager 140may communicate with, instruct, and/or control some or all elements ofsystem 100, such as data agents 142 and media agents 144. In thismanner, storage manager 140 manages the operation of various hardwareand software components in system 100. In certain embodiments, controlinformation originates from storage manager 140 and status as well asindex reporting is transmitted to storage manager 140 by the managedcomponents, whereas payload data and metadata are generally communicatedbetween data agents 142 and media agents 144 (or otherwise betweenclient computing device(s) 102 and secondary storage computing device(s)106), e.g., at the direction of and under the management of storagemanager 140. Control information can generally include parameters andinstructions for carrying out information management operations, suchas, without limitation, instructions to perform a task associated withan operation, timing information specifying when to initiate a task,data path information specifying what components to communicate with oraccess in carrying out an operation, and the like. In other embodiments,some information management operations are controlled or initiated byother components of system 100 (e.g., by media agents 144 or data agents142), instead of or in combination with storage manager 140.

According to certain embodiments, storage manager 140 provides one ormore of the following functions:

-   -   communicating with data agents 142 and media agents 144,        including transmitting instructions, messages, and/or queries,        as well as receiving status reports, index information,        messages, and/or queries, and responding to same;    -   initiating execution of information management operations;    -   initiating restore and recovery operations;    -   managing secondary storage devices 108 and inventory/capacity of        the same;    -   allocating secondary storage devices 108 for secondary copy        operations;    -   reporting, searching, and/or classification of data in system        100;    -   monitoring completion of and status reporting related to        information management operations and jobs;    -   tracking movement of data within system 100;    -   tracking age information relating to secondary copies 116,        secondary storage devices 108, comparing the age information        against retention guidelines, and initiating data pruning when        appropriate;    -   tracking logical associations between components in system 100;    -   protecting metadata associated with system 100, e.g., in        management database 146;    -   implementing job management, schedule management, event        management, alert management, reporting, job history        maintenance, user security management, disaster recovery        management, and/or user interfacing for system administrators        and/or end users of system 100;    -   sending, searching, and/or viewing of log files; and    -   implementing operations management functionality.

Storage manager 140 may maintain an associated database 146 (or “storagemanager database 146” or “management database 146”) ofmanagement-related data and information management policies 148.Database 146 is stored in computer memory accessible by storage manager140. Database 146 may include a management index 150 (or “index 150”) orother data structure(s) that may store: logical associations betweencomponents of the system; user preferences and/or profiles (e.g.,preferences regarding encryption, compression, or deduplication ofprimary data or secondary copies; preferences regarding the scheduling,type, or other aspects of secondary copy or other operations; mappingsof particular information management users or user accounts to certaincomputing devices or other components, etc.; management tasks; mediacontainerization; other useful data; and/or any combination thereof. Forexample, storage manager 140 may use index 150 to track logicalassociations between media agents 144 and secondary storage devices 108and/or movement of data to/from secondary storage devices 108. Forinstance, index 150 may store data associating a client computing device102 with a particular media agent 144 and/or secondary storage device108, as specified in an information management policy 148.

Administrators and others may configure and initiate certain informationmanagement operations on an individual basis. But while this may beacceptable for some recovery operations or other infrequent tasks, it isoften not workable for implementing on-going organization-wide dataprotection and management. Thus, system 100 may utilize informationmanagement policies 148 for specifying and executing informationmanagement operations on an automated basis. Generally, an informationmanagement policy 148 can include a stored data structure or otherinformation source that specifies parameters (e.g., criteria and rules)associated with storage management or other information managementoperations. Storage manager 140 can process an information managementpolicy 148 and/or index 150 and, based on the results, identify aninformation management operation to perform, identify the appropriatecomponents in system 100 to be involved in the operation (e.g., clientcomputing devices 102 and corresponding data agents 142, secondarystorage computing devices 106 and corresponding media agents 144, etc.),establish connections to those components and/or between thosecomponents, and/or instruct and control those components to carry outthe operation. In this manner, system 100 can translate storedinformation into coordinated activity among the various computingdevices in system 100.

Management database 146 may maintain information management policies 148and associated data, although information management policies 148 can bestored in computer memory at any appropriate location outside managementdatabase 146. For instance, an information management policy 148 such asa storage policy may be stored as metadata in a media agent database 152or in a secondary storage device 108 (e.g., as an archive copy) for usein restore or other information management operations, depending on theembodiment. Information management policies 148 are described furtherbelow. According to certain embodiments, management database 146comprises a relational database (e.g., an SQL database) for trackingmetadata, such as metadata associated with secondary copy operations(e.g., what client computing devices 102 and corresponding subclientdata were protected and where the secondary copies are stored and whichmedia agent 144 performed the storage operation(s)). This and othermetadata may additionally be stored in other locations, such as atsecondary storage computing device 106 or on the secondary storagedevice 108, allowing data recovery without the use of storage manager140 in some cases. Thus, management database 146 may comprise dataneeded to kick off secondary copy operations (e.g., storage policies,schedule policies, etc.), status and reporting information aboutcompleted jobs (e.g., status and error reports on yesterday's backupjobs), and additional information sufficient to enable restore anddisaster recovery operations (e.g., media agent associations, locationindexing, content indexing, etc.).

Storage manager 140 may include a jobs agent 156, a user interface 158,and a management agent 154, all of which may be implemented asinterconnected software modules or application programs. These aredescribed further below.

Jobs agent 156 in some embodiments initiates, controls, and/or monitorsthe status of some or all information management operations previouslyperformed, currently being performed, or scheduled to be performed bysystem 100. A job is a logical grouping of information managementoperations such as daily storage operations scheduled for a certain setof subclients (e.g., generating incremental block-level backup copies116 at a certain time every day for database files in a certaingeographical location). Thus, jobs agent 156 may access informationmanagement policies 148 (e.g., in management database 146) to determinewhen, where, and how to initiate/control jobs in system 100.

a. Storage Manager User Interfaces

User interface 158 may include information processing and displaysoftware, such as a graphical user interface (GUI), an applicationprogram interface (API), and/or other interactive interface(s) throughwhich users and system processes can retrieve information about thestatus of information management operations or issue instructions tostorage manager 140 and other components. Via user interface 158, usersmay issue instructions to the components in system 100 regardingperformance of secondary copy and recovery operations. For example, auser may modify a schedule concerning the number of pending secondarycopy operations. As another example, a user may employ the GUI to viewthe status of pending secondary copy jobs or to monitor the status ofcertain components in system 100 (e.g., the amount of capacity left in astorage device). Storage manager 140 may track information that permitsit to select, designate, or otherwise identify content indices,deduplication databases, or similar databases or resources or data setswithin its information management cell (or another cell) to be searchedin response to certain queries. Such queries may be entered by the userby interacting with user interface 158.

Various embodiments of information management system 100 may beconfigured and/or designed to generate user interface data usable forrendering the various interactive user interfaces described. The userinterface data may be used by system 100 and/or by another system,device, and/or software program (for example, a browser program), torender the interactive user interfaces. The interactive user interfacesmay be displayed on, for example, electronic displays (including, forexample, touch-enabled displays), consoles, etc., whetherdirect-connected to storage manager 140 or communicatively coupledremotely, e.g., via an internet connection. The present disclosuredescribes various embodiments of interactive and dynamic userinterfaces, some of which may be generated by user interface agent 158,and which are the result of significant technological development. Theuser interfaces described herein may provide improved human-computerinteractions, allowing for significant cognitive and ergonomicefficiencies and advantages over previous systems, including reducedmental workloads, improved decision-making, and the like. User interface158 may operate in a single integrated view or console (not shown). Theconsole may support a reporting capability for generating a variety ofreports, which may be tailored to a particular aspect of informationmanagement.

User interfaces are not exclusive to storage manager 140 and in someembodiments a user may access information locally from a computingdevice component of system 100. For example, some information pertainingto installed data agents 142 and associated data streams may beavailable from client computing device 102. Likewise, some informationpertaining to media agents 144 and associated data streams may beavailable from secondary storage computing device 106.

b. Storage Manager Management Agent

Management agent 154 can provide storage manager 140 with the ability tocommunicate with other components within system 100 and/or with otherinformation management cells via network protocols and applicationprogramming interfaces (APIs) including, e.g., HTTP, HTTPS, FTP, REST,virtualization software APIs, cloud service provider APIs, and hostedservice provider APIs, without limitation. Management agent 154 alsoallows multiple information management cells to communicate with oneanother. For example, system 100 in some cases may be one informationmanagement cell in a network of multiple cells adjacent to one anotheror otherwise logically related, e.g., in a WAN or LAN. With thisarrangement, the cells may communicate with one another throughrespective management agents 154. Inter-cell communications andhierarchy is described in greater detail in e.g., U.S. Pat. No.7,343,453.

2. Information Management Cell

An “information management cell” (or “storage operation cell” or “cell”)may generally include a logical and/or physical grouping of acombination of hardware and software components associated withperforming information management operations on electronic data,typically one storage manager 140 and at least one data agent 142(executing on a client computing device 102) and at least one mediaagent 144 (executing on a secondary storage computing device 106). Forinstance, the components shown in FIG. 1C may together form aninformation management cell. Thus, in some configurations, a system 100may be referred to as an information management cell or a storageoperation cell. A given cell may be identified by the identity of itsstorage manager 140, which is generally responsible for managing thecell.

Multiple cells may be organized hierarchically, so that cells mayinherit properties from hierarchically superior cells or be controlledby other cells in the hierarchy (automatically or otherwise).Alternatively, in some embodiments, cells may inherit or otherwise beassociated with information management policies, preferences,information management operational parameters, or other properties orcharacteristics according to their relative position in a hierarchy ofcells. Cells may also be organized hierarchically according to function,geography, architectural considerations, or other factors useful ordesirable in performing information management operations. For example,a first cell may represent a geographic segment of an enterprise, suchas a Chicago office, and a second cell may represent a differentgeographic segment, such as a New York City office. Other cells mayrepresent departments within a particular office, e.g., human resources,finance, engineering, etc. Where delineated by function, a first cellmay perform one or more first types of information management operations(e.g., one or more first types of secondary copies at a certainfrequency), and a second cell may perform one or more second types ofinformation management operations (e.g., one or more second types ofsecondary copies at a different frequency and under different retentionrules). In general, the hierarchical information is maintained by one ormore storage managers 140 that manage the respective cells (e.g., incorresponding management database(s) 146).

3. Data Agents

A variety of different applications 110 can operate on a given clientcomputing device 102, including operating systems, file systems,database applications, e-mail applications, and virtual machines, justto name a few. And, as part of the process of creating and restoringsecondary copies 116, the client computing device 102 may be tasked withprocessing and preparing the primary data 112 generated by these variousapplications 110. Moreover, the nature of the processing/preparation candiffer across application types, e.g., due to inherent structural,state, and formatting differences among applications 110 and/or theoperating system of client computing device 102. Each data agent 142 istherefore advantageously configured in some embodiments to assist in theperformance of information management operations based on the type ofdata that is being protected at a client-specific and/orapplication-specific level.

Data agent 142 is a component of information system 100 and is generallydirected by storage manager 140 to participate in creating or restoringsecondary copies 116. Data agent 142 may be a software program (e.g., inthe form of a set of executable binary files) that executes on the sameclient computing device 102 as the associated application 110 that dataagent 142 is configured to protect. Data agent 142 is generallyresponsible for managing, initiating, or otherwise assisting in theperformance of information management operations in reference to itsassociated application(s) 110 and corresponding primary data 112 whichis generated/accessed by the particular application(s) 110. Forinstance, data agent 142 may take part in copying, archiving, migrating,and/or replicating of certain primary data 112 stored in the primarystorage device(s) 104. Data agent 142 may receive control informationfrom storage manager 140, such as commands to transfer copies of dataobjects and/or metadata to one or more media agents 144. Data agent 142also may compress, deduplicate, and encrypt certain primary data 112, aswell as capture application-related metadata before transmitting theprocessed data to media agent 144. Data agent 142 also may receiveinstructions from storage manager 140 to restore (or assist inrestoring) a secondary copy 116 from secondary storage device 108 toprimary storage 104, such that the restored data may be properlyaccessed by application 110 in a suitable format as though it wereprimary data 112.

Each data agent 142 may be specialized for a particular application 110.For instance, different individual data agents 142 may be designed tohandle Microsoft Exchange data, Lotus Notes data, Microsoft Windows filesystem data, Microsoft Active Directory Objects data, SQL Server data,SharePoint data, Oracle database data, SAP database data, virtualmachines and/or associated data, and other types of data. A file systemdata agent, for example, may handle data files and/or other file systeminformation. If a client computing device 102 has two or more types ofdata 112, a specialized data agent 142 may be used for each data type.For example, to backup, migrate, and/or restore all of the data on aMicrosoft Exchange server, the client computing device 102 may use: (1)a Microsoft Exchange Mailbox data agent 142 to back up the Exchangemailboxes; (2) a Microsoft Exchange Database data agent 142 to back upthe Exchange databases; (3) a Microsoft Exchange Public Folder dataagent 142 to back up the Exchange Public Folders; and (4) a MicrosoftWindows File System data agent 142 to back up the file system of clientcomputing device 102. In this example, these specialized data agents 142are treated as four separate data agents 142 even though they operate onthe same client computing device 102. Other examples may include archivemanagement data agents such as a migration archiver or a compliancearchiver, Quick Recovery® agents, and continuous data replicationagents. Application-specific data agents 142 can provide improvedperformance as compared to generic agents. For instance, becauseapplication-specific data agents 142 may only handle data for a singlesoftware application, the design, operation, and performance of the dataagent 142 can be streamlined. The data agent 142 may therefore executefaster and consume less persistent storage and/or operating memory thandata agents designed to generically accommodate multiple differentsoftware applications 110.

Each data agent 142 may be configured to access data and/or metadatastored in the primary storage device(s) 104 associated with data agent142 and its host client computing device 102, and process the dataappropriately. For example, during a secondary copy operation, dataagent 142 may arrange or assemble the data and metadata into one or morefiles having a certain format (e.g., a particular backup or archiveformat) before transferring the file(s) to a media agent 144 or othercomponent. The file(s) may include a list of files or other metadata. Insome embodiments, a data agent 142 may be distributed between clientcomputing device 102 and storage manager 140 (and any other intermediatecomponents) or may be deployed from a remote location or its functionsapproximated by a remote process that performs some or all of thefunctions of data agent 142. In addition, a data agent 142 may performsome functions provided by media agent 144. Other embodiments may employone or more generic data agents 142 that can handle and process datafrom two or more different applications 110, or that can handle andprocess multiple data types, instead of or in addition to usingspecialized data agents 142. For example, one generic data agent 142 maybe used to back up, migrate and restore Microsoft Exchange Mailbox dataand Microsoft Exchange Database data, while another generic data agentmay handle Microsoft Exchange Public Folder data and Microsoft WindowsFile System data.

4. Media Agents

As noted, off-loading certain responsibilities from client computingdevices 102 to intermediate components such as secondary storagecomputing device(s) 106 and corresponding media agent(s) 144 can providea number of benefits including improved performance of client computingdevice 102, faster and more reliable information management operations,and enhanced scalability. In one example which will be discussed furtherbelow, media agent 144 can act as a local cache of recently-copied dataand/or metadata stored to secondary storage device(s) 108, thusimproving restore capabilities and performance for the cached data.

Media agent 144 is a component of system 100 and is generally directedby storage manager 140 in creating and restoring secondary copies 116.Whereas storage manager 140 generally manages system 100 as a whole,media agent 144 provides a portal to certain secondary storage devices108, such as by having specialized features for communicating with andaccessing certain associated secondary storage device 108. Media agent144 may be a software program (e.g., in the form of a set of executablebinary files) that executes on a secondary storage computing device 106.Media agent 144 generally manages, coordinates, and facilitates thetransmission of data between a data agent 142 (executing on clientcomputing device 102) and secondary storage device(s) 108 associatedwith media agent 144. For instance, other components in the system mayinteract with media agent 144 to gain access to data stored onassociated secondary storage device(s) 108, (e.g., to browse, read,write, modify, delete, or restore data). Moreover, media agents 144 cangenerate and store information relating to characteristics of the storeddata and/or metadata, or can generate and store other types ofinformation that generally provides insight into the contents of thesecondary storage devices 108—generally referred to as indexing of thestored secondary copies 116. Each media agent 144 may operate on adedicated secondary storage computing device 106, while in otherembodiments a plurality of media agents 144 may operate on the samesecondary storage computing device 106.

A media agent 144 may be associated with a particular secondary storagedevice 108 if that media agent 144 is capable of one or more of: routingand/or storing data to the particular secondary storage device 108;coordinating the routing and/or storing of data to the particularsecondary storage device 108; retrieving data from the particularsecondary storage device 108; coordinating the retrieval of data fromthe particular secondary storage device 108; and modifying and/ordeleting data retrieved from the particular secondary storage device108. Media agent 144 in certain embodiments is physically separate fromthe associated secondary storage device 108. For instance, a media agent144 may operate on a secondary storage computing device 106 in adistinct housing, package, and/or location from the associated secondarystorage device 108. In one example, a media agent 144 operates on afirst server computer and is in communication with a secondary storagedevice(s) 108 operating in a separate rack-mounted RAID-based system.

A media agent 144 associated with a particular secondary storage device108 may instruct secondary storage device 108 to perform an informationmanagement task. For instance, a media agent 144 may instruct a tapelibrary to use a robotic arm or other retrieval means to load or eject acertain storage media, and to subsequently archive, migrate, or retrievedata to or from that media, e.g., for the purpose of restoring data to aclient computing device 102. As another example, a secondary storagedevice 108 may include an array of hard disk drives or solid statedrives organized in a RAID configuration, and media agent 144 mayforward a logical unit number (LUN) and other appropriate information tothe array, which uses the received information to execute the desiredsecondary copy operation. Media agent 144 may communicate with asecondary storage device 108 via a suitable communications link, such asa SCSI or Fibre Channel link.

Each media agent 144 may maintain an associated media agent database152. Media agent database 152 may be stored to a disk or other storagedevice (not shown) that is local to the secondary storage computingdevice 106 on which media agent 144 executes. In other cases, mediaagent database 152 is stored separately from the host secondary storagecomputing device 106. Media agent database 152 can include, among otherthings, a media agent index 153 (see, e.g., FIG. 1C). In some cases,media agent index 153 does not form a part of and is instead separatefrom media agent database 152.

Media agent index 153 (or “index 153”) may be a data structureassociated with the particular media agent 144 that includes informationabout the stored data associated with the particular media agent andwhich may be generated in the course of performing a secondary copyoperation or a restore. Index 153 provides a fast and efficientmechanism for locating/browsing secondary copies 116 or other datastored in secondary storage devices 108 without having to accesssecondary storage device 108 to retrieve the information from there. Forinstance, for each secondary copy 116, index 153 may include metadatasuch as a list of the data objects (e.g., files/subdirectories, databaseobjects, mailbox objects, etc.), a logical path to the secondary copy116 on the corresponding secondary storage device 108, locationinformation (e.g., offsets) indicating where the data objects are storedin the secondary storage device 108, when the data objects were createdor modified, etc. Thus, index 153 includes metadata associated with thesecondary copies 116 that is readily available for use from media agent144. In some embodiments, some or all of the information in index 153may instead or additionally be stored along with secondary copies 116 insecondary storage device 108. In some embodiments, a secondary storagedevice 108 can include sufficient information to enable a “bare metalrestore,” where the operating system and/or software applications of afailed client computing device 102 or another target may beautomatically restored without manually reinstalling individual softwarepackages (including operating systems).

Because index 153 may operate as a cache, it can also be referred to asan “index cache.” In such cases, information stored in index cache 153typically comprises data that reflects certain particulars aboutrelatively recent secondary copy operations. After some triggeringevent, such as after some time elapses or index cache 153 reaches aparticular size, certain portions of index cache 153 may be copied ormigrated to secondary storage device 108, e.g., on a least-recently-usedbasis. This information may be retrieved and uploaded back into indexcache 153 or otherwise restored to media agent 144 to facilitateretrieval of data from the secondary storage device(s) 108. In someembodiments, the cached information may include format orcontainerization information related to archives or other files storedon storage device(s) 108.

In some alternative embodiments media agent 144 generally acts as acoordinator or facilitator of secondary copy operations between clientcomputing devices 102 and secondary storage devices 108, but does notactually write the data to secondary storage device 108. For instance,storage manager 140 (or media agent 144) may instruct a client computingdevice 102 and secondary storage device 108 to communicate with oneanother directly. In such a case, client computing device 102 transmitsdata directly or via one or more intermediary components to secondarystorage device 108 according to the received instructions, and viceversa. Media agent 144 may still receive, process, and/or maintainmetadata related to the secondary copy operations, i.e., may continue tobuild and maintain index 153. In these embodiments, payload data canflow through media agent 144 for the purposes of populating index 153,but not for writing to secondary storage device 108. Media agent 144and/or other components such as storage manager 140 may in some casesincorporate additional functionality, such as data classification,content indexing, deduplication, encryption, compression, and the like.Further details regarding these and other functions are described below.

H. Distributed, Scalable Architecture

As described, certain functions of system 100 can be distributed amongstvarious physical and/or logical components. For instance, one or more ofstorage manager 140, data agents 142, and media agents 144 may operateon computing devices that are physically separate from one another. Thisarchitecture can provide a number of benefits. For instance, hardwareand software design choices for each distributed component can betargeted to suit its particular function. The secondary computingdevices 106 on which media agents 144 operate can be tailored forinteraction with associated secondary storage devices 108 and providefast index cache operation, among other specific tasks. Similarly,client computing device(s) 102 can be selected to effectively serviceapplications 110 in order to efficiently produce and store primary data112.

Moreover, in some cases, one or more of the individual components ofinformation management system 100 can be distributed to multipleseparate computing devices. As one example, for large file systems wherethe amount of data stored in management database 146 is relativelylarge, database 146 may be migrated to or may otherwise reside on aspecialized database server (e.g., an SQL server) separate from a serverthat implements the other functions of storage manager 140. Thisdistributed configuration can provide added protection because database146 can be protected with standard database utilities (e.g., SQL logshipping or database replication) independent from other functions ofstorage manager 140. Database 146 can be efficiently replicated to aremote site for use in the event of a disaster or other data loss at theprimary site. Or database 146 can be replicated to another computingdevice within the same site, such as to a higher performance machine inthe event that a storage manager host computing device can no longerservice the needs of a growing system 100.

The distributed architecture also provides scalability and efficientcomponent utilization. FIG. 1D shows an embodiment of informationmanagement system 100 including a plurality of client computing devices102 and associated data agents 142 as well as a plurality of secondarystorage computing devices 106 and associated media agents 144.Additional components can be added or subtracted based on the evolvingneeds of system 100. For instance, depending on where bottlenecks areidentified, administrators can add additional client computing devices102, secondary storage computing devices 106, and/or secondary storagedevices 108. Moreover, where multiple fungible components are available,load balancing can be implemented to dynamically address identifiedbottlenecks. As an example, storage manager 140 may dynamically selectwhich media agents 144 and/or secondary storage devices 108 to use forstorage operations based on a processing load analysis of media agents144 and/or secondary storage devices 108, respectively.

Where system 100 includes multiple media agents 144 (see, e.g., FIG.1D), a first media agent 144 may provide failover functionality for asecond failed media agent 144. In addition, media agents 144 can bedynamically selected to provide load balancing. Each client computingdevice 102 can communicate with, among other components, any of themedia agents 144, e.g., as directed by storage manager 140. And eachmedia agent 144 may communicate with, among other components, any ofsecondary storage devices 108, e.g., as directed by storage manager 140.Thus, operations can be routed to secondary storage devices 108 in adynamic and highly flexible manner, to provide load balancing, failover,etc. Further examples of scalable systems capable of dynamic storageoperations, load balancing, and failover are provided in U.S. Pat. No.7,246,207.

While distributing functionality amongst multiple computing devices canhave certain advantages, in other contexts it can be beneficial toconsolidate functionality on the same computing device. In alternativeconfigurations, certain components may reside and execute on the samecomputing device. As such, in other embodiments, one or more of thecomponents shown in FIG. 1C may be implemented on the same computingdevice. In one configuration, a storage manager 140, one or more dataagents 142, and/or one or more media agents 144 are all implemented onthe same computing device. In other embodiments, one or more data agents142 and one or more media agents 144 are implemented on the samecomputing device, while storage manager 140 is implemented on a separatecomputing device, etc. without limitation.

I. Exemplary Types of Information Management Operations, IncludingStorage Operations

In order to protect and leverage stored data, system 100 can beconfigured to perform a variety of information management operations,which may also be referred to in some cases as storage managementoperations or storage operations. These operations can generally include(i) data movement operations, (ii) processing and data manipulationoperations, and (iii) analysis, reporting, and management operations.

1. Data Movement Operations, Including Secondary Copy Operations

Data movement operations are generally storage operations that involvethe copying or migration of data between different locations in system100. For example, data movement operations can include operations inwhich stored data is copied, migrated, or otherwise transferred from oneor more first storage devices to one or more second storage devices,such as from primary storage device(s) 104 to secondary storagedevice(s) 108, from secondary storage device(s) 108 to differentsecondary storage device(s) 108, from secondary storage devices 108 toprimary storage devices 104, or from primary storage device(s) 104 todifferent primary storage device(s) 104, or in some cases within thesame primary storage device 104 such as within a storage array.

Data movement operations can include by way of example, backupoperations, archive operations, information lifecycle managementoperations such as hierarchical storage management operations,replication operations (e.g., continuous data replication), snapshotoperations, deduplication or single-instancing operations, auxiliarycopy operations, disaster-recovery copy operations, and the like. Aswill be discussed, some of these operations do not necessarily createdistinct copies. Nonetheless, some or all of these operations aregenerally referred to as “secondary copy operations” for simplicity,because they involve secondary copies. Data movement also comprisesrestoring secondary copies.

a. Backup Operations

A backup operation creates a copy of a version of primary data 112 at aparticular point in time (e.g., one or more files or other data units).Each subsequent backup copy 116 (which is a form of secondary copy 116)may be maintained independently of the first. A backup generallyinvolves maintaining a version of the copied primary data 112 as well asbackup copies 116. Further, a backup copy in some embodiments is can bestored in a form that is different from the native format, e.g., abackup format for long term storage. This contrasts to the version inprimary data 112 which may instead be stored in a format native to thesource application(s) 110. In various cases, backup copies can be storedin a format in which the data is compressed, encrypted, deduplicated,and/or otherwise modified from the original native application format.For example, a backup copy may be stored in a compressed backup formatthat facilitates efficient long-term storage. Backup copies 116 can haverelatively long retention periods as compared to primary data 112, whichis generally highly changeable. Backup copies 116 may be stored on mediawith slower retrieval times than primary storage device 104. Some backupcopies may have shorter retention periods than some other types ofsecondary copies 116, such as archive copies (described below). In suchsituations the backup copies may be stored in its native format. Backupsmay be stored at an offsite location.

Backup operations can include full backups, differential backups,incremental backups, “synthetic full” backups, and/or creating a“reference copy.” A full backup (or “standard full backup”) in someembodiments is generally a complete image of the data to be protected.However, because full backup copies can consume a relatively largeamount of storage, it can be useful to use a full backup copy as abaseline and only store changes relative to the full backup copyafterwards.

A differential backup operation (or cumulative incremental backupoperation) tracks and stores changes that occurred since the last fullbackup. Differential backups can grow quickly in size, but can restorerelatively efficiently because a restore can be completed in some casesusing only the full backup copy and the latest differential copy.

An incremental backup operation generally tracks and stores changessince the most recent backup copy of any type, which can greatly reducestorage utilization. In some cases, however, restoring can be lengthycompared to full or differential backups because completing a restoreoperation may involve accessing a full backup in addition to multipleincremental backups.

Synthetic full backups generally consolidate data without directlybacking up data from the client computing device. A synthetic fullbackup is created from the most recent full backup (i.e., standard orsynthetic) and subsequent incremental and/or differential backups. Theresulting synthetic full backup is identical to what would have beencreated had the last backup for the subclient been a standard fullbackup. Unlike standard full, incremental, and differential backups,however, a synthetic full backup does not actually transfer data fromprimary storage to the backup media, because it operates as a backupconsolidator. A synthetic full backup extracts the index data of eachparticipating subclient. Using this index data and the previously backedup user data images, it builds new full backup images (e.g., bitmaps),one for each subclient. The new backup images consolidate the index anduser data stored in the related incremental, differential, and previousfull backups into a synthetic backup file that fully represents thesubclient (e.g., via pointers) but does not comprise all its constituentdata.

Any of the above types of backup operations can be at the volume level,file level, or block level. Volume level backup operations generallyinvolve copying of a data volume (e.g., a logical disk or partition) asa whole. In a file-level backup, information management system 100generally tracks changes to individual files and includes copies offiles in the backup copy. For block-level backups, files are broken intoconstituent blocks, and changes are tracked at the block level. Uponrestore, system 100 reassembles the blocks into files in a transparentfashion. Far less data may actually be transferred and copied tosecondary storage devices 108 during a file-level copy than avolume-level copy. Likewise, a block-level copy may transfer less datathan a file-level copy, resulting in faster execution. However,restoring a relatively higher-granularity copy can result in longerrestore times. For instance, when restoring a block-level copy, theprocess of locating and retrieving constituent blocks can sometimes takelonger than restoring file-level backups.

A reference copy may comprise copy(ies) of selected objects from backedup data, typically to help organize data by keeping contextualinformation from multiple sources together, and/or help retain specificdata for a longer period of time, such as for legal hold needs. Areference copy generally maintains data integrity, and when the data isrestored, it may be viewed in the same format as the source data. Insome embodiments, a reference copy is based on a specialized client,individual subclient and associated information management policies(e.g., storage policy, retention policy, etc.) that are administeredwithin system 100.

b. Archive Operations

Because backup operations generally involve maintaining a version of thecopied primary data 112 and also maintaining backup copies in secondarystorage device(s) 108, they can consume significant storage capacity. Toreduce storage consumption, an archive operation according to certainembodiments creates an archive copy 116 by both copying and removingsource data. Or, seen another way, archive operations can involve movingsome or all of the source data to the archive destination. Thus, datasatisfying criteria for removal (e.g., data of a threshold age or size)may be removed from source storage. The source data may be primary data112 or a secondary copy 116, depending on the situation. As with backupcopies, archive copies can be stored in a format in which the data iscompressed, encrypted, deduplicated, and/or otherwise modified from theformat of the original application or source copy. In addition, archivecopies may be retained for relatively long periods of time (e.g., years)and, in some cases are never deleted. In certain embodiments, archivecopies may be made and kept for extended periods in order to meetcompliance regulations.

Archiving can also serve the purpose of freeing up space in primarystorage device(s) 104 and easing the demand on computational resourceson client computing device 102. Similarly, when a secondary copy 116 isarchived, the archive copy can therefore serve the purpose of freeing upspace in the source secondary storage device(s) 108. Examples of dataarchiving operations are provided in U.S. Pat. No. 7,107,298.

c. Snapshot Operations

Snapshot operations can provide a relatively lightweight, efficientmechanism for protecting data. From an end-user viewpoint, a snapshotmay be thought of as an “instant” image of primary data 112 at a givenpoint in time, and may include state and/or status information relativeto an application 110 that creates/manages primary data 112. In oneembodiment, a snapshot may generally capture the directory structure ofan object in primary data 112 such as a file or volume or other data setat a particular moment in time and may also preserve file attributes andcontents. A snapshot in some cases is created relatively quickly, e.g.,substantially instantly, using a minimum amount of file space, but maystill function as a conventional file system backup.

A “hardware snapshot” (or “hardware-based snapshot”) operation occurswhere a target storage device (e.g., a primary storage device 104 or asecondary storage device 108) performs the snapshot operation in aself-contained fashion, substantially independently, using hardware,firmware and/or software operating on the storage device itself. Forinstance, the storage device may perform snapshot operations generallywithout intervention or oversight from any of the other components ofthe system 100, e.g., a storage array may generate an “array-created”hardware snapshot and may also manage its storage, integrity,versioning, etc. In this manner, hardware snapshots can off-load othercomponents of system 100 from snapshot processing. An array may receivea request from another component to take a snapshot and then proceed toexecute the “hardware snapshot” operations autonomously, preferablyreporting success to the requesting component.

A “software snapshot” (or “software-based snapshot”) operation, on theother hand, occurs where a component in system 100 (e.g., clientcomputing device 102, etc.) implements a software layer that manages thesnapshot operation via interaction with the target storage device. Forinstance, the component executing the snapshot management software layermay derive a set of pointers and/or data that represents the snapshot.The snapshot management software layer may then transmit the same to thetarget storage device, along with appropriate instructions for writingthe snapshot. One example of a software snapshot product is MicrosoftVolume Snapshot Service (VSS), which is part of the Microsoft Windowsoperating system.

Some types of snapshots do not actually create another physical copy ofall the data as it existed at the particular point in time, but maysimply create pointers that map files and directories to specific memorylocations (e.g., to specific disk blocks) where the data resides as itexisted at the particular point in time. For example, a snapshot copymay include a set of pointers derived from the file system or from anapplication. In some other cases, the snapshot may be created at theblock-level, such that creation of the snapshot occurs without awarenessof the file system. Each pointer points to a respective stored datablock, so that collectively, the set of pointers reflect the storagelocation and state of the data object (e.g., file(s) or volume(s) ordata set(s)) at the point in time when the snapshot copy was created.

An initial snapshot may use only a small amount of disk space needed torecord a mapping or other data structure representing or otherwisetracking the blocks that correspond to the current state of the filesystem. Additional disk space is usually required only when files anddirectories change later on. Furthermore, when files change, typicallyonly the pointers which map to blocks are copied, not the blocksthemselves. For example for “copy-on-write” snapshots, when a blockchanges in primary storage, the block is copied to secondary storage orcached in primary storage before the block is overwritten in primarystorage, and the pointer to that block is changed to reflect the newlocation of that block. The snapshot mapping of file system data mayalso be updated to reflect the changed block(s) at that particular pointin time. In some other cases, a snapshot includes a full physical copyof all or substantially all of the data represented by the snapshot.Further examples of snapshot operations are provided in U.S. Pat. No.7,529,782. A snapshot copy in many cases can be made quickly and withoutsignificantly impacting primary computing resources because largeamounts of data need not be copied or moved. In some embodiments, asnapshot may exist as a virtual file system, parallel to the actual filesystem. Users in some cases gain read-only access to the record of filesand directories of the snapshot. By electing to restore primary data 112from a snapshot taken at a given point in time, users may also returnthe current file system to the state of the file system that existedwhen the snapshot was taken.

d. Replication Operations

Replication is another type of secondary copy operation. Some types ofsecondary copies 116 periodically capture images of primary data 112 atparticular points in time (e.g., backups, archives, and snapshots).However, it can also be useful for recovery purposes to protect primarydata 112 in a more continuous fashion, by replicating primary data 112substantially as changes occur. In some cases a replication copy can bea mirror copy, for instance, where changes made to primary data 112 aremirrored or substantially immediately copied to another location (e.g.,to secondary storage device(s) 108). By copying each write operation tothe replication copy, two storage systems are kept synchronized orsubstantially synchronized so that they are virtually identical atapproximately the same time. Where entire disk volumes are mirrored,however, mirroring can require significant amount of storage space andutilizes a large amount of processing resources.

According to some embodiments, secondary copy operations are performedon replicated data that represents a recoverable state, or “known goodstate” of a particular application running on the source system. Forinstance, in certain embodiments, known good replication copies may beviewed as copies of primary data 112. This feature allows the system todirectly access, copy, restore, back up, or otherwise manipulate thereplication copies as if they were the “live” primary data 112. This canreduce access time, storage utilization, and impact on sourceapplications 110, among other benefits. Based on known good stateinformation, system 100 can replicate sections of application data thatrepresent a recoverable state rather than rote copying of blocks ofdata. Examples of replication operations (e.g., continuous datareplication) are provided in U.S. Pat. No. 7,617,262.

e. Deduplication/Single-Instancing Operations

Deduplication or single-instance storage is useful to reduce the amountof non-primary data. For instance, some or all of the above-describedsecondary copy operations can involve deduplication in some fashion. Newdata is read, broken down into data portions of a selected granularity(e.g., sub-file level blocks, files, etc.), compared with correspondingportions that are already in secondary storage, and only new/changedportions are stored. Portions that already exist are represented aspointers to the already-stored data. Thus, a deduplicated secondary copy116 may comprise actual data portions copied from primary data 112 andmay further comprise pointers to already-stored data, which is generallymore storage-efficient than a full copy.

In order to streamline the comparison process, system 100 may calculateand/or store signatures (e.g., hashes or cryptographically unique IDs)corresponding to the individual source data portions and compare thesignatures to already-stored data signatures, instead of comparingentire data portions. In some cases, only a single instance of each dataportion is stored, and deduplication operations may therefore bereferred to interchangeably as “single-instancing” operations. Dependingon the implementation, however, deduplication operations can store morethan one instance of certain data portions, yet still significantlyreduce stored-data redundancy. Depending on the embodiment,deduplication portions such as data blocks can be of fixed or variablelength. Using variable length blocks can enhance deduplication byresponding to changes in the data stream, but can involve more complexprocessing. In some cases, system 100 utilizes a technique fordynamically aligning deduplication blocks based on changing content inthe data stream, as described in U.S. Pat. No. 8,364,652.

System 100 can deduplicate in a variety of manners at a variety oflocations. For instance, in some embodiments, system 100 implements“target-side” deduplication by deduplicating data at the media agent 144after being received from data agent 142. In some such cases, mediaagents 144 are generally configured to manage the deduplication process.For instance, one or more of the media agents 144 maintain acorresponding deduplication database that stores deduplicationinformation (e.g., datablock signatures). Examples of such aconfiguration are provided in U.S. Pat. No. 9,020,900. Instead of or incombination with “target-side” deduplication, “source-side” (or“client-side”) deduplication can also be performed, e.g., to reduce theamount of data to be transmitted by data agent 142 to media agent 144.Storage manager 140 may communicate with other components within system100 via network protocols and cloud service provider APIs to facilitatecloud-based deduplication/single instancing, as exemplified in U.S. Pat.No. 8,954,446. Some other deduplication/single instancing techniques aredescribed in U.S. Pat. Pub. No. 2006/0224846 and in U.S. Pat. No.9,098,495.

f. Information Lifecycle Management and Hierarchical Storage Management

In some embodiments, files and other data over their lifetime move frommore expensive quick-access storage to less expensive slower-accessstorage. Operations associated with moving data through various tiers ofstorage are sometimes referred to as information lifecycle management(ILM) operations.

One type of ILM operation is a hierarchical storage management (HSM)operation, which generally automatically moves data between classes ofstorage devices, such as from high-cost to low-cost storage devices. Forinstance, an HSM operation may involve movement of data from primarystorage devices 104 to secondary storage devices 108, or between tiersof secondary storage devices 108. With each tier, the storage devicesmay be progressively cheaper, have relatively slower access/restoretimes, etc. For example, movement of data between tiers may occur asdata becomes less important over time. In some embodiments, an HSMoperation is similar to archiving in that creating an HSM copy may(though not always) involve deleting some of the source data, e.g.,according to one or more criteria related to the source data. Forexample, an HSM copy may include primary data 112 or a secondary copy116 that exceeds a given size threshold or a given age threshold. Often,and unlike some types of archive copies, HSM data that is removed oraged from the source is replaced by a logical reference pointer or stub.The reference pointer or stub can be stored in the primary storagedevice 104 or other source storage device, such as a secondary storagedevice 108 to replace the deleted source data and to point to orotherwise indicate the new location in (another) secondary storagedevice 108.

For example, files are generally moved between higher and lower coststorage depending on how often the files are accessed. When a userrequests access to HSM data that has been removed or migrated, system100 uses the stub to locate the data and may make recovery of the dataappear transparent, even though the HSM data may be stored at a locationdifferent from other source data. In this manner, the data appears tothe user (e.g., in file system browsing windows and the like) as if itstill resides in the source location (e.g., in a primary storage device104). The stub may include metadata associated with the correspondingdata, so that a file system and/or application can provide someinformation about the data object and/or a limited-functionality version(e.g., a preview) of the data object.

An HSM copy may be stored in a format other than the native applicationformat (e.g., compressed, encrypted, deduplicated, and/or otherwisemodified). In some cases, copies which involve the removal of data fromsource storage and the maintenance of stub or other logical referenceinformation on source storage may be referred to generally as “on-linearchive copies.” On the other hand, copies which involve the removal ofdata from source storage without the maintenance of stub or otherlogical reference information on source storage may be referred to as“off-line archive copies.” Examples of HSM and ILM techniques areprovided in U.S. Pat. No. 7,343,453.

g. Auxiliary Copy Operations

An auxiliary copy is generally a copy of an existing secondary copy 116.For instance, an initial secondary copy 116 may be derived from primarydata 112 or from data residing in secondary storage subsystem 118,whereas an auxiliary copy is generated from the initial secondary copy116. Auxiliary copies provide additional standby copies of data and mayreside on different secondary storage devices 108 than the initialsecondary copies 116. Thus, auxiliary copies can be used for recoverypurposes if initial secondary copies 116 become unavailable. Exemplaryauxiliary copy techniques are described in further detail in U.S. Pat.No. 8,230,195.

h. Disaster-Recovery Copy Operations

System 100 may also make and retain disaster recovery copies, often assecondary, high-availability disk copies. System 100 may createsecondary copies and store them at disaster recovery locations usingauxiliary copy or replication operations, such as continuous datareplication technologies. Depending on the particular data protectiongoals, disaster recovery locations can be remote from the clientcomputing devices 102 and primary storage devices 104, remote from someor all of the secondary storage devices 108, or both.

2. Data Manipulation, Including Encryption and Compression

Data manipulation and processing may include encryption and compressionas well as integrity marking and checking, formatting for transmission,formatting for storage, etc. Data may be manipulated “client-side” bydata agent 142 as well as “target-side” by media agent 144 in the courseof creating secondary copy 116, or conversely in the course of restoringdata from secondary to primary.

a. Encryption Operations

System 100 in some cases is configured to process data (e.g., files orother data objects, primary data 112, secondary copies 116, etc.),according to an appropriate encryption algorithm (e.g., Blowfish,Advanced Encryption Standard (AES), Triple Data Encryption Standard(3-DES), etc.) to limit access and provide data security. System 100 insome cases encrypts the data at the client level, such that clientcomputing devices 102 (e.g., data agents 142) encrypt the data prior totransferring it to other components, e.g., before sending the data tomedia agents 144 during a secondary copy operation. In such cases,client computing device 102 may maintain or have access to an encryptionkey or passphrase for decrypting the data upon restore. Encryption canalso occur when media agent 144 creates auxiliary copies or archivecopies. Encryption may be applied in creating a secondary copy 116 of apreviously unencrypted secondary copy 116, without limitation. Infurther embodiments, secondary storage devices 108 can implementbuilt-in, high performance hardware-based encryption.

b. Compression Operations

Similar to encryption, system 100 may also or alternatively compressdata in the course of generating a secondary copy 116. Compressionencodes information such that fewer bits are needed to represent theinformation as compared to the original representation. Compressiontechniques are well known in the art. Compression operations may applyone or more data compression algorithms. Compression may be applied increating a secondary copy 116 of a previously uncompressed secondarycopy, e.g., when making archive copies or disaster recovery copies. Theuse of compression may result in metadata that specifies the nature ofthe compression, so that data may be uncompressed on restore ifappropriate.

3. Data Analysis, Reporting, and Management Operations

Data analysis, reporting, and management operations can differ from datamovement operations in that they do not necessarily involve copying,migration or other transfer of data between different locations in thesystem. For instance, data analysis operations may involve processing(e.g., offline processing) or modification of already stored primarydata 112 and/or secondary copies 116. However, in some embodiments dataanalysis operations are performed in conjunction with data movementoperations. Some data analysis operations include content indexingoperations and classification operations which can be useful inleveraging data under management to enhance search and other features.

a. Classification Operations/Content Indexing

In some embodiments, information management system 100 analyzes andindexes characteristics, content, and metadata associated with primarydata 112 (“online content indexing”) and/or secondary copies 116(“off-line content indexing”). Content indexing can identify files orother data objects based on content (e.g., user-defined keywords orphrases, other keywords/phrases that are not defined by a user, etc.),and/or metadata (e.g., email metadata such as “to,” “from,” “cc,” “bcc,”attachment name, received time, etc.). Content indexes may be searchedand search results may be restored.

System 100 generally organizes and catalogues the results into a contentindex, which may be stored within media agent database 152, for example.The content index can also include the storage locations of or pointerreferences to indexed data in primary data 112 and/or secondary copies116. Results may also be stored elsewhere in system 100 (e.g., inprimary storage device 104 or in secondary storage device 108). Suchcontent index data provides storage manager 140 or other components withan efficient mechanism for locating primary data 112 and/or secondarycopies 116 of data objects that match particular criteria, thus greatlyincreasing the search speed capability of system 100. For instance,search criteria can be specified by a user through user interface 158 ofstorage manager 140. Moreover, when system 100 analyzes data and/ormetadata in secondary copies 116 to create an “off-line content index,”this operation has no significant impact on the performance of clientcomputing devices 102 and thus does not take a toll on the productionenvironment. Examples of content indexing techniques are provided inU.S. Pat. No. 8,170,995.

One or more components, such as a content index engine, can beconfigured to scan data and/or associated metadata for classificationpurposes to populate a database (or other data structure) ofinformation, which can be referred to as a “data classificationdatabase” or a “metabase.” Depending on the embodiment, the dataclassification database(s) can be organized in a variety of differentways, including centralization, logical sub-divisions, and/or physicalsub-divisions. For instance, one or more data classification databasesmay be associated with different subsystems or tiers within system 100.As an example, there may be a first metabase associated with primarystorage subsystem 117 and a second metabase associated with secondarystorage subsystem 118. In other cases, metabase(s) may be associatedwith individual components, e.g., client computing devices 102 and/ormedia agents 144. In some embodiments, a data classification databasemay reside as one or more data structures within management database146, may be otherwise associated with storage manager 140, and/or mayreside as a separate component. In some cases, metabase(s) may beincluded in separate database(s) and/or on separate storage device(s)from primary data 112 and/or secondary copies 116, such that operationsrelated to the metabase(s) do not significantly impact performance onother components of system 100. In other cases, metabase(s) may bestored along with primary data 112 and/or secondary copies 116. Files orother data objects can be associated with identifiers (e.g., tagentries, etc.) to facilitate searches of stored data objects. Among anumber of other benefits, the metabase can also allow efficient,automatic identification of files or other data objects to associatewith secondary copy or other information management operations. Forinstance, a metabase can dramatically improve the speed with whichsystem 100 can search through and identify data as compared to otherapproaches that involve scanning an entire file system. Examples ofmetabases and data classification operations are provided in U.S. Pat.Nos. 7,734,669 and 7,747,579.

b. Management and Reporting Operations

Certain embodiments leverage the integrated ubiquitous nature of system100 to provide useful system-wide management and reporting. Operationsmanagement can generally include monitoring and managing the health andperformance of system 100 by, without limitation, performing errortracking, generating granular storage/performance metrics (e.g., jobsuccess/failure information, deduplication efficiency, etc.), generatingstorage modeling and costing information, and the like. As an example,storage manager 140 or another component in system 100 may analyzetraffic patterns and suggest and/or automatically route data to minimizecongestion. In some embodiments, the system can generate predictionsrelating to storage operations or storage operation information. Suchpredictions, which may be based on a trending analysis, may predictvarious network operations or resource usage, such as network trafficlevels, storage media use, use of bandwidth of communication links, useof media agent components, etc. Further examples of traffic analysis,trend analysis, prediction generation, and the like are described inU.S. Pat. No. 7,343,453.

In some configurations having a hierarchy of storage operation cells, amaster storage manager 140 may track the status of subordinate cells,such as the status of jobs, system components, system resources, andother items, by communicating with storage managers 140 (or othercomponents) in the respective storage operation cells. Moreover, themaster storage manager 140 may also track status by receiving periodicstatus updates from the storage managers 140 (or other components) inthe respective cells regarding jobs, system components, systemresources, and other items. In some embodiments, a master storagemanager 140 may store status information and other information regardingits associated storage operation cells and other system information inits management database 146 and/or index 150 (or in another location).The master storage manager 140 or other component may also determinewhether certain storage-related or other criteria are satisfied, and mayperform an action or trigger event (e.g., data migration) in response tothe criteria being satisfied, such as where a storage threshold is metfor a particular volume, or where inadequate protection exists forcertain data. For instance, data from one or more storage operationcells is used to dynamically and automatically mitigate recognizedrisks, and/or to advise users of risks or suggest actions to mitigatethese risks. For example, an information management policy may specifycertain requirements (e.g., that a storage device should maintain acertain amount of free space, that secondary copies should occur at aparticular interval, that data should be aged and migrated to otherstorage after a particular period, that data on a secondary volumeshould always have a certain level of availability and be restorablewithin a given time period, that data on a secondary volume may bemirrored or otherwise migrated to a specified number of other volumes,etc.). If a risk condition or other criterion is triggered, the systemmay notify the user of these conditions and may suggest (orautomatically implement) a mitigation action to address the risk. Forexample, the system may indicate that data from a primary copy 112should be migrated to a secondary storage device 108 to free up space onprimary storage device 104. Examples of the use of risk factors andother triggering criteria are described in U.S. Pat. No. 7,343,453.

In some embodiments, system 100 may also determine whether a metric orother indication satisfies particular storage criteria sufficient toperform an action. For example, a storage policy or other definitionmight indicate that a storage manager 140 should initiate a particularaction if a storage metric or other indication drops below or otherwisefails to satisfy specified criteria such as a threshold of dataprotection. In some embodiments, risk factors may be quantified intocertain measurable service or risk levels. For example, certainapplications and associated data may be considered to be more importantrelative to other data and services. Financial compliance data, forexample, may be of greater importance than marketing materials, etc.Network administrators may assign priority values or “weights” tocertain data and/or applications corresponding to the relativeimportance. The level of compliance of secondary copy operationsspecified for these applications may also be assigned a certain value.Thus, the health, impact, and overall importance of a service may bedetermined, such as by measuring the compliance value and calculatingthe product of the priority value and the compliance value to determinethe “service level” and comparing it to certain operational thresholdsto determine whether it is acceptable. Further examples of the servicelevel determination are provided in U.S. Pat. No. 7,343,453.

System 100 may additionally calculate data costing and data availabilityassociated with information management operation cells. For instance,data received from a cell may be used in conjunction withhardware-related information and other information about system elementsto determine the cost of storage and/or the availability of particulardata. Exemplary information generated could include how fast aparticular department is using up available storage space, how long datawould take to recover over a particular pathway from a particularsecondary storage device, costs over time, etc. Moreover, in someembodiments, such information may be used to determine or predict theoverall cost associated with the storage of certain information. Thecost associated with hosting a certain application may be based, atleast in part, on the type of media on which the data resides, forexample. Storage devices may be assigned to a particular cost category,for example. Further examples of costing techniques are described inU.S. Pat. No. 7,343,453.

Any of the above types of information (e.g., information related totrending, predictions, job, cell or component status, risk, servicelevel, costing, etc.) can generally be provided to users via userinterface 158 in a single integrated view or console (not shown). Reporttypes may include: scheduling, event management, media management anddata aging. Available reports may also include backup history, dataaging history, auxiliary copy history, job history, library and drive,media in library, restore history, and storage policy, etc., withoutlimitation. Such reports may be specified and created at a certain pointin time as a system analysis, forecasting, or provisioning tool.Integrated reports may also be generated that illustrate storage andperformance metrics, risks and storage costing information. Moreover,users may create their own reports based on specific needs. Userinterface 158 can include an option to graphically depict the variouscomponents in the system using appropriate icons. As one example, userinterface 158 may provide a graphical depiction of primary storagedevices 104, secondary storage devices 108, data agents 142 and/or mediaagents 144, and their relationship to one another in system 100.

In general, the operations management functionality of system 100 canfacilitate planning and decision-making. For example, in someembodiments, a user may view the status of some or all jobs as well asthe status of each component of information management system 100. Usersmay then plan and make decisions based on this data. For instance, auser may view high-level information regarding secondary copy operationsfor system 100, such as job status, component status, resource status(e.g., communication pathways, etc.), and other information. The usermay also drill down or use other means to obtain more detailedinformation regarding a particular component, job, or the like. Furtherexamples are provided in U.S. Pat. No. 7,343,453.

System 100 can also be configured to perform system-wide e-discoveryoperations in some embodiments. In general, e-discovery operationsprovide a unified collection and search capability for data in thesystem, such as data stored in secondary storage devices 108 (e.g.,backups, archives, or other secondary copies 116). For example, system100 may construct and maintain a virtual repository for data stored insystem 100 that is integrated across source applications 110, differentstorage device types, etc. According to some embodiments, e-discoveryutilizes other techniques described herein, such as data classificationand/or content indexing.

J. Information Management Policies

An information management policy 148 can include a data structure orother information source that specifies a set of parameters (e.g.,criteria and rules) associated with secondary copy and/or otherinformation management operations.

One type of information management policy 148 is a “storage policy.”According to certain embodiments, a storage policy generally comprises adata structure or other information source that defines (or includesinformation sufficient to determine) a set of preferences or othercriteria for performing information management operations. Storagepolicies can include one or more of the following: (1) what data will beassociated with the storage policy, e.g., subclient; (2) a destinationto which the data will be stored; (3) datapath information specifyinghow the data will be communicated to the destination; (4) the type ofsecondary copy operation to be performed; and (5) retention informationspecifying how long the data will be retained at the destination (see,e.g., FIG. 1E). Data associated with a storage policy can be logicallyorganized into subclients, which may represent primary data 112 and/orsecondary copies 116. A subclient may represent static or dynamicassociations of portions of a data volume. Subclients may representmutually exclusive portions. Thus, in certain embodiments, a portion ofdata may be given a label and the association is stored as a staticentity in an index, database or other storage location. Subclients mayalso be used as an effective administrative scheme of organizing dataaccording to data type, department within the enterprise, storagepreferences, or the like. Depending on the configuration, subclients cancorrespond to files, folders, virtual machines, databases, etc. In oneexemplary scenario, an administrator may find it preferable to separatee-mail data from financial data using two different subclients.

A storage policy can define where data is stored by specifying a targetor destination storage device (or group of storage devices). Forinstance, where the secondary storage device 108 includes a group ofdisk libraries, the storage policy may specify a particular disk libraryfor storing the subclients associated with the policy. As anotherexample, where the secondary storage devices 108 include one or moretape libraries, the storage policy may specify a particular tape libraryfor storing the subclients associated with the storage policy, and mayalso specify a drive pool and a tape pool defining a group of tapedrives and a group of tapes, respectively, for use in storing thesubclient data. While information in the storage policy can bestatically assigned in some cases, some or all of the information in thestorage policy can also be dynamically determined based on criteria setforth in the storage policy. For instance, based on such criteria, aparticular destination storage device(s) or other parameter of thestorage policy may be determined based on characteristics associatedwith the data involved in a particular secondary copy operation, deviceavailability (e.g., availability of a secondary storage device 108 or amedia agent 144), network status and conditions (e.g., identifiedbottlenecks), user credentials, and the like.

Datapath information can also be included in the storage policy. Forinstance, the storage policy may specify network pathways and componentsto utilize when moving the data to the destination storage device(s). Insome embodiments, the storage policy specifies one or more media agents144 for conveying data associated with the storage policy between thesource and destination. A storage policy can also specify the type(s) ofassociated operations, such as backup, archive, snapshot, auxiliarycopy, or the like. Furthermore, retention parameters can specify howlong the resulting secondary copies 116 will be kept (e.g., a number ofdays, months, years, etc.), perhaps depending on organizational needsand/or compliance criteria.

When adding a new client computing device 102, administrators canmanually configure information management policies 148 and/or othersettings, e.g., via user interface 158. However, this can be an involvedprocess resulting in delays, and it may be desirable to begin dataprotection operations quickly, without awaiting human intervention.Thus, in some embodiments, system 100 automatically applies a defaultconfiguration to client computing device 102. As one example, when oneor more data agent(s) 142 are installed on a client computing device102, the installation script may register the client computing device102 with storage manager 140, which in turn applies the defaultconfiguration to the new client computing device 102. In this manner,data protection operations can begin substantially immediately. Thedefault configuration can include a default storage policy, for example,and can specify any appropriate information sufficient to begin dataprotection operations. This can include a type of data protectionoperation, scheduling information, a target secondary storage device108, data path information (e.g., a particular media agent 144), and thelike.

Another type of information management policy 148 is a “schedulingpolicy,” which specifies when and how often to perform operations.Scheduling parameters may specify with what frequency (e.g., hourly,weekly, daily, event-based, etc.) or under what triggering conditionssecondary copy or other information management operations are to takeplace. Scheduling policies in some cases are associated with particularcomponents, such as a subclient, client computing device 102, and thelike.

Another type of information management policy 148 is an “audit policy”(or “security policy”), which comprises preferences, rules and/orcriteria that protect sensitive data in system 100. For example, anaudit policy may define “sensitive objects” which are files or dataobjects that contain particular keywords (e.g., “confidential,” or“privileged”) and/or are associated with particular keywords (e.g., inmetadata) or particular flags (e.g., in metadata identifying a documentor email as personal, confidential, etc.). An audit policy may furtherspecify rules for handling sensitive objects. As an example, an auditpolicy may require that a reviewer approve the transfer of any sensitiveobjects to a cloud storage site, and that if approval is denied for aparticular sensitive object, the sensitive object should be transferredto a local primary storage device 104 instead. To facilitate thisapproval, the audit policy may further specify how a secondary storagecomputing device 106 or other system component should notify a reviewerthat a sensitive object is slated for transfer.

Another type of information management policy 148 is a “provisioningpolicy,” which can include preferences, priorities, rules, and/orcriteria that specify how client computing devices 102 (or groupsthereof) may utilize system resources, such as available storage oncloud storage and/or network bandwidth. A provisioning policy specifies,for example, data quotas for particular client computing devices 102(e.g., a number of gigabytes that can be stored monthly, quarterly orannually). Storage manager 140 or other components may enforce theprovisioning policy. For instance, media agents 144 may enforce thepolicy when transferring data to secondary storage devices 108. If aclient computing device 102 exceeds a quota, a budget for the clientcomputing device 102 (or associated department) may be adjustedaccordingly or an alert may trigger.

While the above types of information management policies 148 aredescribed as separate policies, one or more of these can be generallycombined into a single information management policy 148. For instance,a storage policy may also include or otherwise be associated with one ormore scheduling, audit, or provisioning policies or operationalparameters thereof. Moreover, while storage policies are typicallyassociated with moving and storing data, other policies may beassociated with other types of information management operations. Thefollowing is a non-exhaustive list of items that information managementpolicies 148 may specify:

-   -   schedules or other timing information, e.g., specifying when        and/or how often to perform information management operations;    -   the type of secondary copy 116 and/or copy format (e.g.,        snapshot, backup, archive, HSM, etc.);    -   a location or a class or quality of storage for storing        secondary copies 116 (e.g., one or more particular secondary        storage devices 108);    -   preferences regarding whether and how to encrypt, compress,        deduplicate, or otherwise modify or transform secondary copies        116;    -   which system components and/or network pathways (e.g., preferred        media agents 144) should be used to perform secondary storage        operations;    -   resource allocation among different computing devices or other        system components used in performing information management        operations (e.g., bandwidth allocation, available storage        capacity, etc.);    -   whether and how to synchronize or otherwise distribute files or        other data objects across multiple computing devices or hosted        services; and    -   retention information specifying the length of time primary data        112 and/or secondary copies 116 should be retained, e.g., in a        particular class or tier of storage devices, or within the        system 100.

Information management policies 148 can additionally specify or dependon historical or current criteria that may be used to determine whichrules to apply to a particular data object, system component, orinformation management operation, such as:

-   -   frequency with which primary data 112 or a secondary copy 116 of        a data object or metadata has been or is predicted to be used,        accessed, or modified;    -   time-related factors (e.g., aging information such as time since        the creation or modification of a data object);    -   deduplication information (e.g., hashes, data blocks,        deduplication block size, deduplication efficiency or other        metrics);    -   an estimated or historic usage or cost associated with different        components (e.g., with secondary storage devices 108);    -   the identity of users, applications 110, client computing        devices 102 and/or other computing devices that created,        accessed, modified, or otherwise utilized primary data 112 or        secondary copies 116;    -   a relative sensitivity (e.g., confidentiality, importance) of a        data object, e.g., as determined by its content and/or metadata;    -   the current or historical storage capacity of various storage        devices;    -   the current or historical network capacity of network pathways        connecting various components within the storage operation cell;    -   access control lists or other security information; and    -   the content of a particular data object (e.g., its textual        content) or of metadata associated with the data object.

1. Exemplary Storage Policy and Secondary Copy Operations

FIG. 1E includes a data flow diagram depicting performance of secondarycopy operations by an embodiment of information management system 100,according to an exemplary storage policy 148A. System 100 includes astorage manager 140, a client computing device 102 having a file systemdata agent 142A and an email data agent 142B operating thereon, aprimary storage device 104, two media agents 144A, 144B, and twosecondary storage devices 108: a disk library 108A and a tape library108B. As shown, primary storage device 104 includes primary data 112A,which is associated with a logical grouping of data associated with afile system (“file system subclient”), and primary data 112B, which is alogical grouping of data associated with email (“email subclient”). Thetechniques described with respect to FIG. 1E can be utilized inconjunction with data that is otherwise organized as well.

As indicated by the dashed box, the second media agent 144B and tapelibrary 108B are “off-site,” and may be remotely located from the othercomponents in system 100 (e.g., in a different city, office building,etc.). Indeed, “off-site” may refer to a magnetic tape located in remotestorage, which must be manually retrieved and loaded into a tape driveto be read. In this manner, information stored on the tape library 108Bmay provide protection in the event of a disaster or other failure atthe main site(s) where data is stored.

The file system subclient 112A in certain embodiments generallycomprises information generated by the file system and/or operatingsystem of client computing device 102, and can include, for example,file system data (e.g., regular files, file tables, mount points, etc.),operating system data (e.g., registries, event logs, etc.), and thelike. The e-mail subclient 112B can include data generated by an e-mailapplication operating on client computing device 102, e.g., mailboxinformation, folder information, emails, attachments, associateddatabase information, and the like. As described above, the subclientscan be logical containers, and the data included in the correspondingprimary data 112A and 112B may or may not be stored contiguously.

The exemplary storage policy 148A includes backup copy preferences orrule set 160, disaster recovery copy preferences or rule set 162, andcompliance copy preferences or rule set 164. Backup copy rule set 160specifies that it is associated with file system subclient 166 and emailsubclient 168. Each of subclients 166 and 168 are associated with theparticular client computing device 102. Backup copy rule set 160 furtherspecifies that the backup operation will be written to disk library 108Aand designates a particular media agent 144A to convey the data to disklibrary 108A. Finally, backup copy rule set 160 specifies that backupcopies created according to rule set 160 are scheduled to be generatedhourly and are to be retained for 30 days. In some other embodiments,scheduling information is not included in storage policy 148A and isinstead specified by a separate scheduling policy.

Disaster recovery copy rule set 162 is associated with the same twosubclients 166 and 168. However, disaster recovery copy rule set 162 isassociated with tape library 108B, unlike backup copy rule set 160.Moreover, disaster recovery copy rule set 162 specifies that a differentmedia agent, namely 144B, will convey data to tape library 108B.Disaster recovery copies created according to rule set 162 will beretained for 60 days and will be generated daily. Disaster recoverycopies generated according to disaster recovery copy rule set 162 canprovide protection in the event of a disaster or other catastrophic dataloss that would affect the backup copy 116A maintained on disk library108A.

Compliance copy rule set 164 is only associated with the email subclient168, and not the file system subclient 166. Compliance copies generatedaccording to compliance copy rule set 164 will therefore not includeprimary data 112A from the file system subclient 166. For instance, theorganization may be under an obligation to store and maintain copies ofemail data fora particular period of time (e.g., 10 years) to complywith state or federal regulations, while similar regulations do notapply to file system data. Compliance copy rule set 164 is associatedwith the same tape library 108B and media agent 144B as disasterrecovery copy rule set 162, although a different storage device or mediaagent could be used in other embodiments. Finally, compliance copy ruleset 164 specifies that the copies it governs will be generated quarterlyand retained for 10 years.

2. Secondary Copy Jobs

A logical grouping of secondary copy operations governed by a rule setand being initiated at a point in time may be referred to as a“secondary copy job” (and sometimes may be called a “backup job,” eventhough it is not necessarily limited to creating only backup copies).Secondary copy jobs may be initiated on demand as well. Steps 1-9 belowillustrate three secondary copy jobs based on storage policy 148A.

Referring to FIG. 1E, at step 1, storage manager 140 initiates a backupjob according to the backup copy rule set 160, which logically comprisesall the secondary copy operations necessary to effectuate rules 160 instorage policy 148A every hour, including steps 1-4 occurring hourly.For instance, a scheduling service running on storage manager 140accesses backup copy rule set 160 or a separate scheduling policyassociated with client computing device 102 and initiates a backup jobon an hourly basis. Thus, at the scheduled time, storage manager 140sends instructions to client computing device 102 (i.e., to both dataagent 142A and data agent 142B) to begin the backup job.

At step 2, file system data agent 142A and email data agent 142B onclient computing device 102 respond to instructions from storage manager140 by accessing and processing the respective subclient primary data112A and 112B involved in the backup copy operation, which can be foundin primary storage device 104. Because the secondary copy operation is abackup copy operation, the data agent(s) 142A, 142B may format the datainto a backup format or otherwise process the data suitable for a backupcopy.

At step 3, client computing device 102 communicates the processed filesystem data (e.g., using file system data agent 142A) and the processedemail data (e.g., using email data agent 142B) to the first media agent144A according to backup copy rule set 160, as directed by storagemanager 140. Storage manager 140 may further keep a record in managementdatabase 146 of the association between media agent 144A and one or moreof: client computing device 102, file system subclient 112A, file systemdata agent 142A, email subclient 112B, email data agent 142B, and/orbackup copy 116A.

The target media agent 144A receives the data-agent-processed data fromclient computing device 102, and at step 4 generates and conveys backupcopy 116A to disk library 108A to be stored as backup copy 116A, againat the direction of storage manager 140 and according to backup copyrule set 160. Media agent 144A can also update its index 153 to includedata and/or metadata related to backup copy 116A, such as informationindicating where the backup copy 116A resides on disk library 108A,where the email copy resides, where the file system copy resides, dataand metadata for cache retrieval, etc. Storage manager 140 may similarlyupdate its index 150 to include information relating to the secondarycopy operation, such as information relating to the type of operation, aphysical location associated with one or more copies created by theoperation, the time the operation was performed, status informationrelating to the operation, the components involved in the operation, andthe like. In some cases, storage manager 140 may update its index 150 toinclude some or all of the information stored in index 153 of mediaagent 144A. At this point, the backup job may be considered complete.After the 30-day retention period expires, storage manager 140 instructsmedia agent 144A to delete backup copy 116A from disk library 108A andindexes 150 and/or 153 are updated accordingly.

At step 5, storage manager 140 initiates another backup job for adisaster recovery copy according to the disaster recovery rule set 162.Illustratively this includes steps 5-7 occurring daily for creatingdisaster recovery copy 116B. Illustratively, and by way of illustratingthe scalable aspects and off-loading principles embedded in system 100,disaster recovery copy 116B is based on backup copy 116A and not onprimary data 112A and 112B.

At step 6, illustratively based on instructions received from storagemanager 140 at step 5, the specified media agent 144B retrieves the mostrecent backup copy 116A from disk library 108A.

At step 7, again at the direction of storage manager 140 and asspecified in disaster recovery copy rule set 162, media agent 144B usesthe retrieved data to create a disaster recovery copy 116B and store itto tape library 108B. In some cases, disaster recovery copy 116B is adirect, mirror copy of backup copy 116A, and remains in the backupformat. In other embodiments, disaster recovery copy 116B may be furthercompressed or encrypted, or may be generated in some other manner, suchas by using primary data 112A and 112B from primary storage device 104as sources. The disaster recovery copy operation is initiated once a dayand disaster recovery copies 116B are deleted after 60 days; indexes 153and/or 150 are updated accordingly when/after each informationmanagement operation is executed and/or completed. The present backupjob may be considered completed.

At step 8, storage manager 140 initiates another backup job according tocompliance rule set 164, which performs steps 8-9 quarterly to createcompliance copy 116C. For instance, storage manager 140 instructs mediaagent 144B to create compliance copy 116C on tape library 108B, asspecified in the compliance copy rule set 164.

At step 9 in the example, compliance copy 116C is generated usingdisaster recovery copy 116B as the source. This is efficient, becausedisaster recovery copy resides on the same secondary storage device andthus no network resources are required to move the data. In otherembodiments, compliance copy 116C is instead generated using primarydata 112B corresponding to the email subclient or using backup copy 116Afrom disk library 108A as source data. As specified in the illustratedexample, compliance copies 116C are created quarterly, and are deletedafter ten years, and indexes 153 and/or 150 are kept up-to-dateaccordingly.

3. Exemplary Applications of Storage Policies—Information GovernancePolicies and Classification

Again referring to FIG. 1E, storage manager 140 may permit a user tospecify aspects of storage policy 148A. For example, the storage policycan be modified to include information governance policies to define howdata should be managed in order to comply with a certain regulation orbusiness objective. The various policies may be stored, for example, inmanagement database 146. An information governance policy may align withone or more compliance tasks that are imposed by regulations or businessrequirements. Examples of information governance policies might includea Sarbanes-Oxley policy, a HIPAA policy, an electronic discovery(e-discovery) policy, and so on.

Information governance policies allow administrators to obtain differentperspectives on an organization's online and offline data, without theneed for a dedicated data silo created solely for each differentviewpoint. As described previously, the data storage systems hereinbuild an index that reflects the contents of a distributed data set thatspans numerous clients and storage devices, including both primary dataand secondary copies, and online and offline copies. An organization mayapply multiple information governance policies in a top-down manner overthat unified data set and indexing schema in order to view andmanipulate the data set through different lenses, each of which isadapted to a particular compliance or business goal. Thus, for example,by applying an e-discovery policy and a Sarbanes-Oxley policy, twodifferent groups of users in an organization can conduct two verydifferent analyses of the same underlying physical set of data/copies,which may be distributed throughout the information management system.

An information governance policy may comprise a classification policy,which defines a taxonomy of classification terms or tags relevant to acompliance task and/or business objective. A classification policy mayalso associate a defined tag with a classification rule. Aclassification rule defines a particular combination of criteria, suchas users who have created, accessed or modified a document or dataobject; file or application types; content or metadata keywords; clientsor storage locations; dates of data creation and/or access; reviewstatus or other status within a workflow (e.g., reviewed orun-reviewed); modification times or types of modifications; and/or anyother data attributes in any combination, without limitation. Aclassification rule may also be defined using other classification tagsin the taxonomy. The various criteria used to define a classificationrule may be combined in any suitable fashion, for example, via Booleanoperators, to define a complex classification rule. As an example, ane-discovery classification policy might define a classification tag“privileged” that is associated with documents or data objects that (1)were created or modified by legal department staff, or (2) were sent toor received from outside counsel via email, or (3) contain one of thefollowing keywords: “privileged” or “attorney” or “counsel,” or otherlike terms. Accordingly, all these documents or data objects will beclassified as “privileged.”

One specific type of classification tag, which may be added to an indexat the time of indexing, is an “entity tag.” An entity tag may be, forexample, any content that matches a defined data mask format. Examplesof entity tags might include, e.g., social security numbers (e.g., anynumerical content matching the formatting mask XXX-XX-XXXX), credit cardnumbers (e.g., content having a 13-16 digit string of numbers), SKUnumbers, product numbers, etc. A user may define a classification policyby indicating criteria, parameters or descriptors of the policy via agraphical user interface, such as a form or page with fields to befilled in, pull-down menus or entries allowing one or more of severaloptions to be selected, buttons, sliders, hypertext links or other knownuser interface tools for receiving user input, etc. For example, a usermay define certain entity tags, such as a particular product number orproject ID. In some implementations, the classification policy can beimplemented using cloud-based techniques. For example, the storagedevices may be cloud storage devices, and the storage manager 140 mayexecute cloud service provider API over a network to classify datastored on cloud storage devices.

K. Restore Operations from Secondary Copies

While not shown in FIG. 1E, at some later point in time, a restoreoperation can be initiated involving one or more of secondary copies116A, 116B, and 116C. A restore operation logically takes a selectedsecondary copy 116, reverses the effects of the secondary copy operationthat created it, and stores the restored data to primary storage where aclient computing device 102 may properly access it as primary data. Amedia agent 144 and an appropriate data agent 142 (e.g., executing onthe client computing device 102) perform the tasks needed to complete arestore operation. For example, data that was encrypted, compressed,and/or deduplicated in the creation of secondary copy 116 will becorrespondingly rehydrated (reversing deduplication), uncompressed, andunencrypted into a format appropriate to primary data. Metadata storedwithin or associated with the secondary copy 116 may be used during therestore operation. In general, restored data should be indistinguishablefrom other primary data 112. Preferably, the restored data has fullyregained the native format that may make it immediately usable byapplication 110.

As one example, a user may manually initiate a restore of backup copy116A, e.g., by interacting with user interface 158 of storage manager140 or with a web-based console with access to system 100. Storagemanager 140 may accesses data in its index 150 and/or managementdatabase 146 (and/or the respective storage policy 148A) associated withthe selected backup copy 116A to identify the appropriate media agent144A and/or secondary storage device 108A where the secondary copyresides. The user may be presented with a representation (e.g., stub,thumbnail, listing, etc.) and metadata about the selected secondarycopy, in order to determine whether this is the appropriate copy to berestored, e.g., date that the original primary data was created. Storagemanager 140 will then instruct media agent 144A and an appropriate dataagent 142 on the target client computing device 102 to restore secondarycopy 116A to primary storage device 104. A media agent may be selectedfor use in the restore operation based on a load balancing algorithm, anavailability based algorithm, or other criteria. The selected mediaagent, e.g., 144A, retrieves secondary copy 116A from disk library 108A.For instance, media agent 144A may access its index 153 to identify alocation of backup copy 116A on disk library 108A, or may accesslocation information residing on disk library 108A itself.

In some cases a backup copy 116A that was recently created or accessed,may be cached to speed up the restore operation. In such a case, mediaagent 144A accesses a cached version of backup copy 116A residing inindex 153, without having to access disk library 108A for some or all ofthe data. Once it has retrieved backup copy 116A, the media agent 144Acommunicates the data to the requesting client computing device 102.Upon receipt, file system data agent 142A and email data agent 142B mayunpack (e.g., restore from a backup format to the native applicationformat) the data in backup copy 116A and restore the unpackaged data toprimary storage device 104. In general, secondary copies 116 may berestored to the same volume or folder in primary storage device 104 fromwhich the secondary copy was derived; to another storage location orclient computing device 102; to shared storage, etc. In some cases, thedata may be restored so that it may be used by an application 110 of adifferent version/vintage from the application that created the originalprimary data 112.

L. Exemplary Secondary Copy Formatting

The formatting and structure of secondary copies 116 can vary dependingon the embodiment. In some cases, secondary copies 116 are formatted asa series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4GB, or 8 GB chunks). This can facilitate efficient communication andwriting to secondary storage devices 108, e.g., according to resourceavailability. For example, a single secondary copy 116 may be written ona chunk-by-chunk basis to one or more secondary storage devices 108. Insome cases, users can select different chunk sizes, e.g., to improvethroughput to tape storage devices. Generally, each chunk can include aheader and a payload. The payload can include files (or other dataunits) or subsets thereof included in the chunk, whereas the chunkheader generally includes metadata relating to the chunk, some or all ofwhich may be derived from the payload. For example, during a secondarycopy operation, media agent 144, storage manager 140, or other componentmay divide files into chunks and generate headers for each chunk byprocessing the files. Headers can include a variety of information suchas file and/or volume identifier(s), offset(s), and/or other informationassociated with the payload data items, a chunk sequence number, etc.Importantly, in addition to being stored with secondary copy 116 onsecondary storage device 108, chunk headers can also be stored to index153 of the associated media agent(s) 144 and/or to index 150 associatedwith storage manager 140. This can be useful for providing fasterprocessing of secondary copies 116 during browsing, restores, or otheroperations. In some cases, once a chunk is successfully transferred to asecondary storage device 108, the secondary storage device 108 returnsan indication of receipt, e.g., to media agent 144 and/or storagemanager 140, which may update their respective indexes 153, 150accordingly. During restore, chunks may be processed (e.g., by mediaagent 144) according to the information in the chunk header toreassemble the files.

Data can also be communicated within system 100 in data channels thatconnect client computing devices 102 to secondary storage devices 108.These data channels can be referred to as “data streams,” and multipledata streams can be employed to parallelize an information managementoperation, improving data transfer rate, among other advantages. Exampledata formatting techniques including techniques involving datastreaming, chunking, and the use of other data structures in creatingsecondary copies are described in U.S. Pat. Nos. 7,315,923, 8,156,086,and 8,578,120.

FIGS. 1F and 1G are diagrams of example data streams 170 and 171,respectively, which may be employed for performing informationmanagement operations. Referring to FIG. 1F, data agent 142 forms datastream 170 from source data associated with a client computing device102 (e.g., primary data 112). Data stream 170 is composed of multiplepairs of stream header 172 and stream data (or stream payload) 174. Datastreams 170 and 171 shown in the illustrated example are for asingle-instanced storage operation, and a stream payload 174 thereforemay include both single-instance (SI) data and/or non-SI data. A streamheader 172 includes metadata about the stream payload 174. This metadatamay include, for example, a length of the stream payload 174, anindication of whether the stream payload 174 is encrypted, an indicationof whether the stream payload 174 is compressed, an archive fileidentifier (ID), an indication of whether the stream payload 174 issingle instanceable, and an indication of whether the stream payload 174is a start of a block of data.

Referring to FIG. 1G, data stream 171 has the stream header 172 andstream payload 174 aligned into multiple data blocks. In this example,the data blocks are of size 64 KB. The first two stream header 172 andstream payload 174 pairs comprise a first data block of size 64 KB. Thefirst stream header 172 indicates that the length of the succeedingstream payload 174 is 63 KB and that it is the start of a data block.The next stream header 172 indicates that the succeeding stream payload174 has a length of 1 KB and that it is not the start of a new datablock. Immediately following stream payload 174 is a pair comprising anidentifier header 176 and identifier data 178. The identifier header 176includes an indication that the succeeding identifier data 178 includesthe identifier for the immediately previous data block. The identifierdata 178 includes the identifier that the data agent 142 generated forthe data block. The data stream 171 also includes other stream header172 and stream payload 174 pairs, which may be for SI data and/or non-SIdata.

FIG. 1H is a diagram illustrating data structures 180 that may be usedto store blocks of SI data and non-SI data on a storage device (e.g.,secondary storage device 108). According to certain embodiments, datastructures 180 do not form part of a native file system of the storagedevice. Data structures 180 include one or more volume folders 182, oneor more chunk folders 184/185 within the volume folder 182, and multiplefiles within chunk folder 184. Each chunk folder 184/185 includes ametadata file 186/187, a metadata index file 188/189, one or morecontainer files 190/191/193, and a container index file 192/194.Metadata file 186/187 stores non-SI data blocks as well as links to SIdata blocks stored in container files. Metadata index file 188/189stores an index to the data in the metadata file 186/187. Containerfiles 190/191/193 store SI data blocks. Container index file 192/194stores an index to container files 190/191/193. Among other things,container index file 192/194 stores an indication of whether acorresponding block in a container file 190/191/193 is referred to by alink in a metadata file 186/187. For example, data block B2 in thecontainer file 190 is referred to by a link in metadata file 187 inchunk folder 185. Accordingly, the corresponding index entry incontainer index file 192 indicates that data block B2 in container file190 is referred to. As another example, data block B1 in container file191 is referred to by a link in metadata file 187, and so thecorresponding index entry in container index file 192 indicates thatthis data block is referred to.

As an example, data structures 180 illustrated in FIG. 1H may have beencreated as a result of separate secondary copy operations involving twoclient computing devices 102. For example, a first secondary copyoperation on a first client computing device 102 could result in thecreation of the first chunk folder 184, and a second secondary copyoperation on a second client computing device 102 could result in thecreation of the second chunk folder 185. Container files 190/191 in thefirst chunk folder 184 would contain the blocks of SI data of the firstclient computing device 102. If the two client computing devices 102have substantially similar data, the second secondary copy operation onthe data of the second client computing device 102 would result in mediaagent 144 storing primarily links to the data blocks of the first clientcomputing device 102 that are already stored in the container files190/191. Accordingly, while a first secondary copy operation may resultin storing nearly all of the data subject to the operation, subsequentsecondary storage operations involving similar data may result insubstantial data storage space savings, because links to already storeddata blocks can be stored instead of additional instances of datablocks.

If the operating system of the secondary storage computing device 106 onwhich media agent 144 operates supports sparse files, then when mediaagent 144 creates container files 190/191/193, it can create them assparse files. A sparse file is a type of file that may include emptyspace (e.g., a sparse file may have real data within it, such as at thebeginning of the file and/or at the end of the file, but may also haveempty space in it that is not storing actual data, such as a contiguousrange of bytes all having a value of zero). Having container files190/191/193 be sparse files allows media agent 144 to free up space incontainer files 190/191/193 when blocks of data in container files190/191/193 no longer need to be stored on the storage devices. In someexamples, media agent 144 creates a new container file 190/191/193 whena container file 190/191/193 either includes 100 blocks of data or whenthe size of the container file 190 exceeds 50 MB. In other examples,media agent 144 creates a new container file 190/191/193 when acontainer file 190/191/193 satisfies other criteria (e.g., it containsfrom approx. 100 to approx. 1000 blocks or when its size exceedsapproximately 50 MB to 1 GB). In some cases, a file on which a secondarycopy operation is performed may comprise a large number of data blocks.For example, a 100 MB file may comprise 400 data blocks of size 256 KB.If such a file is to be stored, its data blocks may span more than onecontainer file, or even more than one chunk folder. As another example,a database file of 20 GB may comprise over 40,000 data blocks of size512 KB. If such a database file is to be stored, its data blocks willlikely span multiple container files, multiple chunk folders, andpotentially multiple volume folders. Restoring such files may requireaccessing multiple container files, chunk folders, and/or volume foldersto obtain the requisite data blocks.

M. Using Backup Data for Replication and Disaster Recovery (“LiveSynchronization”)

There is an increased demand to off-load resource intensive informationmanagement tasks (e.g., data replication tasks) away from productiondevices (e.g., physical or virtual client computing devices) in order tomaximize production efficiency. At the same time, enterprises expectaccess to readily-available up-to-date recovery copies in the event offailure, with little or no production downtime.

FIG. 2A illustrates a system 200 configured to address these and otherissues by using backup or other secondary copy data to synchronize asource subsystem 201 (e.g., a production site) with a destinationsubsystem 203 (e.g., a failover site). Such a technique can be referredto as “live synchronization” and/or “live synchronization replication.”In the illustrated embodiment, the source client computing devices 202 ainclude one or more virtual machines (or “VMs”) executing on one or morecorresponding VM host computers 205 a, though the source need not bevirtualized. The destination site 203 may be at a location that isremote from the production site 201, or may be located in the same datacenter, without limitation. One or more of the production site 201 anddestination site 203 may reside at data centers at known geographiclocations, or alternatively may operate “in the cloud.”

The synchronization can be achieved by generally applying an ongoingstream of incremental backups from the source subsystem 201 to thedestination subsystem 203, such as according to what can be referred toas an “incremental forever” approach. FIG. 2A illustrates an embodimentof a data flow which may be orchestrated at the direction of one or morestorage managers (not shown). At step 1, the source data agent(s) 242 aand source media agent(s) 244 a work together to write backup or othersecondary copies of the primary data generated by the source clientcomputing devices 202 a into the source secondary storage device(s) 208a. At step 2, the backup/secondary copies are retrieved by the sourcemedia agent(s) 244 a from secondary storage. At step 3, source mediaagent(s) 244 a communicate the backup/secondary copies across a networkto the destination media agent(s) 244 b in destination subsystem 203.

As shown, the data can be copied from source to destination in anincremental fashion, such that only changed blocks are transmitted, andin some cases multiple incremental backups are consolidated at thesource so that only the most current changed blocks are transmitted toand applied at the destination. An example of live synchronization ofvirtual machines using the “incremental forever” approach is found inU.S. Patent Application No. 62/265,339 entitled “Live Synchronizationand Management of Virtual Machines across Computing and VirtualizationPlatforms and Using Live Synchronization to Support Disaster Recovery.”Moreover, a deduplicated copy can be employed to further reduce networktraffic from source to destination. For instance, the system can utilizethe deduplicated copy techniques described in U.S. Pat. No. 9,239,687,entitled “Systems and Methods for Retaining and Using Data BlockSignatures in Data Protection Operations.”

At step 4, destination media agent(s) 244 b write the receivedbackup/secondary copy data to the destination secondary storagedevice(s) 208 b. At step 5, the synchronization is completed when thedestination media agent(s) and destination data agent(s) 242 b restorethe backup/secondary copy data to the destination client computingdevice(s) 202 b. The destination client computing device(s) 202 b may bekept “warm” awaiting activation in case failure is detected at thesource. This synchronization/replication process can incorporate thetechniques described in U.S. patent application Ser. No. 14/721,971,entitled “Replication Using Deduplicated Secondary Copy Data.”

Where the incremental backups are applied on a frequent, on-going basis,the synchronized copies can be viewed as mirror or replication copies.Moreover, by applying the incremental backups to the destination site203 using backup or other secondary copy data, the production site 201is not burdened with the synchronization operations. Because thedestination site 203 can be maintained in a synchronized “warm” state,the downtime for switching over from the production site 201 to thedestination site 203 is substantially less than with a typical restorefrom secondary storage. Thus, the production site 201 may flexibly andefficiently fail over, with minimal downtime and with relativelyup-to-date data, to a destination site 203, such as a cloud-basedfailover site. The destination site 203 can later be reversesynchronized back to the production site 201, such as after repairs havebeen implemented or after the failure has passed.

N. Integrating with the Cloud Using File System Protocols

Given the ubiquity of cloud computing, it can be increasingly useful toprovide data protection and other information management services in ascalable, transparent, and highly plug-able fashion. FIG. 2B illustratesan information management system 200 having an architecture thatprovides such advantages, and incorporates use of a standard file systemprotocol between primary and secondary storage subsystems 217, 218. Asshown, the use of the network file system (NFS) protocol (or any anotherappropriate file system protocol such as that of the Common InternetFile System (CIFS)) allows data agent 242 to be moved from the primarystorage subsystem 217 to the secondary storage subsystem 218. Forinstance, as indicated by the dashed box 206 around data agent 242 andmedia agent 244, data agent 242 can co-reside with media agent 244 onthe same server (e.g., a secondary storage computing device such ascomponent 106), or in some other location in secondary storage subsystem218.

Where NFS is used, for example, secondary storage subsystem 218allocates an NFS network path to the client computing device 202 or toone or more target applications 210 running on client computing device202. During a backup or other secondary copy operation, the clientcomputing device 202 mounts the designated NFS path and writes data tothat NFS path. The NFS path may be obtained from NFS path data 215stored locally at the client computing device 202, and which may be acopy of or otherwise derived from NFS path data 219 stored in thesecondary storage subsystem 218.

Write requests issued by client computing device(s) 202 are received bydata agent 242 in secondary storage subsystem 218, which translates therequests and works in conjunction with media agent 244 to process andwrite data to a secondary storage device(s) 208, thereby creating abackup or other secondary copy. Storage manager 240 can include apseudo-client manager 217, which coordinates the process by, among otherthings, communicating information relating to client computing device202 and application 210 (e.g., application type, client computing deviceidentifier, etc.) to data agent 242, obtaining appropriate NFS path datafrom the data agent 242 (e.g., NFS path information), and deliveringsuch data to client computing device 202.

Conversely, during a restore or recovery operation client computingdevice 202 reads from the designated NFS network path, and the readrequest is translated by data agent 242. The data agent 242 then workswith media agent 244 to retrieve, re-process (e.g., re-hydrate,decompress, decrypt), and forward the requested data to client computingdevice 202 using NFS.

By moving specialized software associated with system 200 such as dataagent 242 off the client computing devices 202, the illustrativearchitecture effectively decouples the client computing devices 202 fromthe installed components of system 200, improving both scalability andplug-ability of system 200. Indeed, the secondary storage subsystem 218in such environments can be treated simply as a read/write NFS targetfor primary storage subsystem 217, without the need for informationmanagement software to be installed on client computing devices 202. Asone example, an enterprise implementing a cloud production computingenvironment can add VM client computing devices 202 without installingand configuring specialized information management software on theseVMs. Rather, backups and restores are achieved transparently, where thenew VMs simply write to and read from the designated NFS path. Anexample of integrating with the cloud using file system protocols orso-called “infinite backup” using NFS share is found in U.S. PatentApplication No. 62/294,920, entitled “Data Protection Operations Basedon Network Path Information.” Examples of improved data restorationscenarios based on network-path information, including using storedbackups effectively as primary data sources, may be found in U.S. PatentApplication No. 62/297,057, entitled “Data Restoration Operations Basedon Network Path Information.”

O. Highly Scalable Managed Data Pool Architecture

Enterprises are seeing explosive data growth in recent years, often fromvarious applications running in geographically distributed locations.FIG. 2C shows a block diagram of an example of a highly scalable,managed data pool architecture useful in accommodating such data growth.The illustrated system 200, which may be referred to as a “web-scale”architecture according to certain embodiments, can be readilyincorporated into both open compute/storage and common-cloudarchitectures.

The illustrated system 200 includes a grid 245 of media agents 244logically organized into a control tier 231 and a secondary or storagetier 233. Media agents assigned to the storage tier 233 can beconfigured to manage a secondary storage pool 208 as a deduplicationstore, and be configured to receive client write and read requests fromthe primary storage subsystem 217, and direct those requests to thesecondary tier 233 for servicing. For instance, media agents CMA1-CMA3in the control tier 231 maintain and consult one or more deduplicationdatabases 247, which can include deduplication information (e.g., datablock hashes, data block links, file containers for deduplicated files,etc.) sufficient to read deduplicated files from secondary storage pool208 and write deduplicated files to secondary storage pool 208. Forinstance, system 200 can incorporate any of the deduplication systemsand methods shown and described in U.S. Pat. No. 9,020,900, entitled“Distributed Deduplicated Storage System,” and U.S. Pat. Pub. No.2014/0201170, entitled “High Availability Distributed DeduplicatedStorage System.”

Media agents SMA1-SMA6 assigned to the secondary tier 233 receive writeand read requests from media agents CMA1-CMA3 in control tier 231, andaccess secondary storage pool 208 to service those requests. Mediaagents CMA1-CMA3 in control tier 231 can also communicate with secondarystorage pool 208, and may execute read and write requests themselves(e.g., in response to requests from other control media agentsCMA1-CMA3) in addition to issuing requests to media agents in secondarytier 233. Moreover, while shown as separate from the secondary storagepool 208, deduplication database(s) 247 can in some cases reside instorage devices in secondary storage pool 208.

As shown, each of the media agents 244 (e.g., CMA1-CMA3, SMA1-SMA6,etc.) in grid 245 can be allocated a corresponding dedicated partition251A-2511, respectively, in secondary storage pool 208. Each partition251 can include a first portion 253 containing data associated with(e.g., stored by) media agent 244 corresponding to the respectivepartition 251. System 200 can also implement a desired level ofreplication, thereby providing redundancy in the event of a failure of amedia agent 244 in grid 245. Along these lines, each partition 251 canfurther include a second portion 255 storing one or more replicationcopies of the data associated with one or more other media agents 244 inthe grid.

System 200 can also be configured to allow for seamless addition ofmedia agents 244 to grid 245 via automatic configuration. As oneillustrative example, a storage manager (not shown) or other appropriatecomponent may determine that it is appropriate to add an additional nodeto control tier 231, and perform some or all of the following: (i)assess the capabilities of a newly added or otherwise availablecomputing device as satisfying a minimum criteria to be configured as orhosting a media agent in control tier 231; (ii) confirm that asufficient amount of the appropriate type of storage exists to supportan additional node in control tier 231 (e.g., enough disk drive capacityexists in storage pool 208 to support an additional deduplicationdatabase 247); (iii) install appropriate media agent software on thecomputing device and configure the computing device according to apre-determined template; (iv) establish a partition 251 in the storagepool 208 dedicated to the newly established media agent 244; and (v)build any appropriate data structures (e.g., an instance ofdeduplication database 247). An example of highly scalable managed datapool architecture or so-called web-scale architecture for storage anddata management is found in U.S. Patent Application No. 62/273,286entitled “Redundant and Robust Distributed Deduplication Data StorageSystem.”

The embodiments and components thereof disclosed in FIGS. 2A, 2B, and2C, as well as those in FIGS. 1A-1H, may be implemented in anycombination and permutation to satisfy data storage management andinformation management needs at one or more locations and/or datacenters.

P. Management of Internet of Thing (IoT) Devices

The disclosed technology communicates with IoT devices to gather andprotect IoT data, such as information related to device failure orerror(s) even if the IoT devices are limited in resources. For example,the disclosed technology can receive log files from a smart refrigeratorthat recently failed even if the smart refrigerator lacks diagnosticsoftware, a large memory, and high processing power. In someimplementations of the disclosed technology, a threshold number of logfile entries are transferred as part of the log file based on one ofmore of the following parameters: type of IoT device, location of IoTdevice, age of IoT device, storage capacity of IoT device, storagecapacity of data agent, bandwidth constraints, SLA requirements forfixing the error (e.g., error is to be fixed within 5 minutes ofdetection, etc.), a predetermined number of log file data entries (e.g.,10 log file data entries), size of the log file (e.g., maximum 10 MB),creation time/date, etc. The disclosed technology can also determinewhich log files the refrigerator created before and/or after a failure.After the disclosed technology gathers this information, it can storethe information in a database, send it to the IoT device-related entity,or send it to a storage environment provided by a cloud provider. Aninformation management system protects IoT data by creating backupcopies. In some implementations, the disclosed technology can send thefailure-related information to the IoT device-related entity (e.g.,manufacturer, supplier, etc.), and the entity uses this information totroubleshoot the failure and send a fix or software update to the IoTdevice.

In some implementations of the disclosed technology, a data agent causesan IoT device to execute instructions to transfer log files associatedwith an error from the IoT device to a storage resource to store the logfiles. For example, a data agent can access a smart refrigerator'smemory using Bluetooth® and install code on the smart refrigerator thatenables the IoT device to send its log files to the storage resource,e.g., if the smart refrigerator experiences an error or failure.

In other implementations, the data agent can generate a snapshot orreplica of the IoT device memory to create a backup. The replica can bea hard drive disk image of part of the IoT device memory or the entirememory depending on policy standards set by a technician. Next, thedisclosed technology can store the replica of the IoT device memory in adatabase, e.g., until failure or error occurs. If a failure or erroroccurs on the IoT device, the disclosed technology can use a data agentto transfer relevant log file data from the IoT device to the databasestoring the replica of the IoT device. Technicians then can view or runsimulations using the replica of the IoT device, along with the log filedata, without communicating with or using the IoT device. One advantageof this disclosed technology is that it aggregates valuable error orfailure information for troubleshooting and replicates memories for IoTdevices. The IoT can also be transmitted to a storage resource, e.g.,cloud storage environment, and be protected for a longer term by makingbackup copies.

In other implementations, a computing device can poll IoT devices, e.g.,to determine whether a failure or error has occurred. Polling includesquerying the IoT device at a certain frequency (e.g., hourly, daily) todetermine if an abnormal condition such as a failure has occurred.Abnormal conditions can be state values of the device that indicateerror or failure such as high current, high temperature, hardware error,or connectivity or sensor problems. A computing device can conduct thepolling. The computing device can be an enhanced router (also referredto as an “IoT monitor”) that uses Bluetooth®, or another component, tocommunicate with IoT devices such as smart TVs, smart refrigerators,and/or smart plugs in a home, without limitation. In someimplementations, if the computing device polls an IoT device anddetermines that an error occurred, the computing device can send thestate conditions of the IoT device to a server or database for furtherprocessing and analysis.

FIG. 3 is a block diagram illustrating an environment 301 for gatheringIoT device data or communicating with IoT devices. The environment 301includes a mobile device 304, IoT devices 302, IoT monitors 305, anetwork 306, client computing devices 102 (FIG. 1A), a storageenvironment provided by a cloud provider 312, and an informationmanagement system 100 that comprises a storage manager 140 (FIG. 1C) anIoT data agent 314, a media agent 144, and one or more electronic datastorage devices 315 (e.g., 315 a, 315 b, 315 c). The blocks areschematic representations of the devices in the environment 301, andeach block is described below in more detail.

The environment 301 can include a variety of IoT devices. The IoTdevices 302 can be wearable devices such a smart watch, a home appliancesuch as a refrigerator or a smoke detector, or an electronic user devicesuch as a smart television, a smart plug, a smart toothbrush, a videocamera, a smart pet feeder, a set of audio speakers, a washer, a dryer,a dishwashing machine, a thermostat, and/or a weather sensor, etc.,without limitation. Some examples of IoT devices are an Ecobee® Smart SiThermostat, an Amazon Echo®, or a Schlage® Camelot Touchscreen Deadboltlock. The environment 301 can be a residence or a campus for anorganization (e.g., college or business). In some implementations, theenvironment 301 is a farmland with hundreds of IoT device sensors.

In environment 301, the mobile device 304 is used to communicate andgather information about the IoT devices 302. A user can use the mobiledevice 304 to input information about the IoT devices 302 into thestorage manager 140, e.g., defining storage entities, subclients,storage and retention policies, etc. For example, a user can takepictures of the IoT devices 302 or the user can input model or serialnumber information for the IoT devices into the mobile device, and themobile device transfers this information through the network to thestorage manager 140. A user can also input IoT device information byusing barcodes, Quick Response codes, or a mobile application (“app”)that automatically detects IoT devices in the environment 301 andqueries a user to determine if the IoT device should be added to thestorage manager for reference.

The IoT monitors 305 communicate with the IoT devices 302. The IoTmonitors 305 connect wirelessly or through wired connections with theIoT devices 302, and the IoT monitors 305 can access the memory of theIoT devices. The IoT monitors 305 can also monitor the IoT devices 302,for example, to determine whether the devices are on, off, orexperiencing failure. To determine how to communicate with IoT devices,the IoT monitor 305 can receive instructions from the storage manager140 regarding the hardware and software specification of the IoT devices302. Based on information from the storage manager 140, the IoT devicecan use one or various protocols to communicate with the IoT devices. Insome implementations, the IoT monitors 305 contain ZigBee® and ZWave®radios, and are also compatible with IP-accessible IoT devices. The IoTmonitors 305 can also communicate with the client computing devices 102,and in some implementations a user can use the client computing devices102 to adjust settings of the IoT monitor 305 or access informationabout the IoT monitor 305. The IoT monitors 305 can also communicatewith the network 306.

As shown in FIG. 3, the environment 301 includes a storage environmentprovided by a cloud provider 312. The storage environment provided bythe cloud provider 312 can include an IoT device-related entity, such asthe manufacturer of the IoT devices 302, or a cloud service such asAmazon Web Services® or Azure®. The client computing devices 102, theIoT monitors 305 (comprising e.g., IoT device data 303), the mobiledevice 304, the storage manager 140, and the network 306 can send IoTdevice data 303 to the storage environment provided by the cloudprovider 312. In some implementations, a technician uses the IoT devicedata 303 stored by the cloud provider to analyze errors, troubleshootdevice failures, and send fixes to the IoT devices. In otherimplementations, the storage manager 140 can send, or cause a data agent314 to send, stored data regarding the IoT devices 302 to the storageenvironment provided by the cloud provider 312. In some implementations,data 303 in cloud storage 312 is protected by way of making backupcopies 316, which can be retained for any amount of time.

As used herein, the IoT device data 303 comprises data (includingmetadata) generated by the IoT device that can be copied and migrated bythe data agent 314, acting as a component of information managementsystem 100. IoT device data 303 can include the IoT device diagnosticrelated data, sensor data, and/or operational data, without limitation.Examples of IoT device data 303 include log files, minidump files,processor memory dumps and register information, dynamically allocatedmemory, hard disk images, state conditions, time stamps, data points,configuration files, message queues, API logs, supervisory control anddata acquisition data, etc., without limitation.

The network 306 can be a local area network (LAN), a wide area network(WAN), a cellular network, a computer network, or a combination ofnetworks that connects the devices shown in FIG. 3. In someimplementations, the network 306 may be the Internet or some otherpublic or private network. The client computing devices 102, the IoTmonitors 305, the IoT devices 302, the information management system100, and the storage environment provided by a cloud provider 312 can beconnected to the network 306 through a network interface, such as bywired or wireless communication as shown by the double-headed arrows inFIG. 3.

The information management system 100 illustrated in FIG. 3 is similarto the information management system described in FIGS. 1A-1H. Theinformation management system 100 comprises elements such as a storagemanager 140, data agent(s) 314, media agent(s) 144, and electronic datastorage device(s) 315. The storage manager 140 may communicate with,instruct, and/or control some or all elements of the informationmanagement system 100 including the IoT data agents 314 and media agents144.

The information management system 100 stores IoT device data 303, in theform of backup copies, e.g., secondary copies 316, in electronic datastorage devices 315 as illustrated in FIG. 3. As illustrated in FIG. 3,the electronic data storage devices 315 (e.g., 315 a, 315 b, 315 c . . .315 n) can generally be of any suitable type including, withoutlimitation, disk drives, storage arrays (e.g., storage-area network(SAN) and/or network-attached storage (NAS) technology), semiconductormemory (e.g., solid state storage devices), tape libraries, or othermagnetic, non-tape storage devices, optical media storage devices,DNA/RNA-based memory technology, combinations of the same, etc. In someembodiments, storage devices form part of a distributed file system. Insome cases, storage devices are provided in a cloud storage environment(e.g., a private cloud or one operated by a third-party vendor)(e.g.,315 b), whether for primary data or secondary copies or both.

The storage manager 140 illustrated in FIG. 3 is similar to the storagemanager 140 described in FIG. 1C. The IoT data agent 314 is similar tothe data agent 142 described in FIG. 1C and the IoT data agent 314includes some additional functionality to enable the transfer ofinformation from IoT devices to one or more of, depending onimplementation: the storage manager 140, the storage environmentprovided by a cloud provider 312, the client computer device 102, andthe electronic data storage devices 315. More generally, the IoT dataagent 314 is a combination of hardware and software that can establishconnections with the IoT devices 302 and gather information about thesedevices. In some implementations, the IoT data agent 314 can sendcomputer-executable instructions to the IoT devices 302 or the IoTmonitors 305 that cause the IoT devices 302 to send log files, performdata dumps, perform backup operations, make replicas or take snapshotsof memory for these devices. In such implementations, the IoT data agent314 may partially or completely exist on the IoT devices 302 or theclient computing devices 102. For example, a user can authorize theinstallation of the IoT data agent 314 on the IoT devices 302, and inputprivacy and control information related to type or information that canbe transferred away from the IoT devices 302. The IoT devices 302 canexecute algorithms that are described in more detail in the textcorresponding with FIG. 5. Alternatively or additionally, depending onimplementation, the IoT data agent 314 may exist on the IoT monitoringdevice 305 as illustrated in FIG. 4B.

As previously described, the storage manager 140 can communicate with,instruct, and/or control media agent(s) 144 which are specializedprogrammed intelligence and/or hardware capable of writing to, readingfrom, instructing, communicating with, or otherwise interacting withelectronic data storage devices 315. Such media agents can be utilizedto make secondary copies of IoT data (e.g., secondary copies 316) thatcan be stored in backup format, archive format, or other formats notnative to the format of the primary data 303.

FIGS. 4A and 4B are block diagrams illustrating more detail for the IoTdevices 302 and the IoT monitors 305 shown in FIG. 3. In particular,FIG. 4A illustrates an example of one of the IoT devices 302 including aprocessor 402, memory 404 with log files 405 and/or a log agent 406and/or state data 407 (dashed lines indicate these are optional,described in more detail below), an input/output (I/O) module 403, and acommunication module 410. The IoT device 302 can vary in size,processing power, memory structure and type, and components, and caninclude all or some of the optional components shown by dashed lines inFIG. 4A. The overall structure of the IoT device 302 generally variesbased on function, for example whether it is a smart TV or smart plug.

Continuing with FIG. 4A, the processor 402 can access the memory 404.The memory 404 can include hardware devices for volatile andnon-volatile storage, and can include both read-only and writablememory. For example, the memory can comprise random access memory (RAM),registers, read-only memory (ROM), and writable non-volatile memory,such as flash memory and hard drives. The memory 404 stores programs,software, and data such as log files 405, a log agent 406, and statedata/conditions 407, each of which is described in more detail in thenext paragraph.

Log files 405 generally include operating conditions or operatinghistory for the IoT device 302. Log files data varies based on the typeof IoT device. Log file categories can include security logs (e.g.,spam, malware, or virus information), authentication logs pertaining tosuccessful/unsuccessful login attempts, general information logs, logsrelated to configuration of devices, firewall logs, and devicemanagement logs, etc., without limitation.

The log agent 406 is software that enables the IoT device 302 to shareits log files. In some implementations, the IoT device 302 may not havea log agent 406, but the IoT data agent 314 can send installationinstructions to the IoT device 302 to install the log agent 406. Statedata 407 can also include configuration data, settings, user options,time stamps, sensor or sensed data, or session identifiers related tothe IoT device, etc., without limitation.

The I/O module 403 enables the processor 402 to be electrically coupledto a network card, video card, audio card, USB, FireWire, or otherexternal device. Also, the communication module 410 includes acommunication device capable of communicating in a wireless orwire-based fashion with a network node, e.g., in network 306. Thecommunication module 410 can communicate with another device or a serverthrough a network using, for example, TCP/IP protocols. In someimplementations, the communication module 410 includes hardware andsoftware for Bluetooth®, ZigBee®, ZigBee Remote Control®, Z-Wave®,6LowPAN®, Thread®, Wi-Fi, cellular, Near Field Communication, SigFox®,Neul®, and LoRaWan®.

Although not illustrated in FIG. 4A, the IoT device may have installedon it an IoT data agent 314 prior to any error occurring with the IoTdevice (e.g., installed at manufacture). The IoT device may download theIoT data agent when the IoT device establishes a network connection andthen connects with a preprogrammed, installer programmed or userprogrammed address (e.g., URL) that the IoT device is to connect to uponpower up or periodically (e.g., weekly/monthly). The IoT data agent canbe modified to have functions distributed across different devices. Thiscan reduce the burden on the limited resource IoT device, which may haveinsufficient memory and/or processing ability to support all thefunctioning requirements of the IoT data agent 314. For instance, theIoT data agent installed at the IoT device can have specializedfunctions only (e.g., making replicas and migrating the data), and theremainder of its functions can be distributed to the IoT data agents 314at the information management system or IoT monitor. Alternatively, theIoT data agent 314 can reside with the IoT monitor and its functionsdistributed between the IoT monitor and the information managementsystem.

Moving to FIG. 4B, the IoT monitor 305 is a physical and/or logicalassociation of hardware and software that monitors one or more of theIoT devices 302. The IoT monitors 305 each include the processor 402,the memory 404, the I/O module 403, the communication module 410, andthe IoT data agent 314. Although these components carry the samereference numbers as components of IoT device 302, they need not bephysically identical or identically configured, depending onimplementation. Optionally, the IoT monitor may also include anelectronic data storage module 405 to store the IoT device data 303obtained from one or more IoT devices 302. The IoT monitor enablesbidirectional communications between IoT devices 302 and a back-endcomputer such as a client or server (e.g., client computing devices 102or storage manager 140). The IoT monitor 305 provides device-to-cloudand cloud-to device communications including file transfer andrequest-reply methods to/from cloud storage 312. The IoT monitor 305 cancommunicate with the IoT devices with no human operator, IoT devices ina remote location, and IoT devices with limited power and processingresources. In some implementations, the IoT monitor also providessecurity. For example, the IoT monitor can authenticate each IoT device302 in the network 306 shown in FIG. 3. In some implementations, the IoTmonitor includes libraries of IoT protocols such as Message QueueTelemetry Transport (MQTT), TCP/IP, Hypertext Transfer Protocol (HTTP),Constrained Application Protocol (CoAP), or Advanced Message Queueingprotocol (AMQP). In other implementations, the IoT monitor 305 can storeor upload custom protocols or convert custom protocols into e.g., MQTT,TCP/IP, HTTP, or AMQP.

FIG. 5 is a flow diagram for implementing a process 500 for transferringIoT device data 303 from an IoT device 302 to a database or other datastructure suitable for storing IoT data 303, e.g., at cloud storage 312,and for making secondary copies 316. Process 500 generally includesestablishing a connection with an IoT device 302, generating a replicaof the IoT device, transferring log files or other IoT data 303 (e.g.,data related to the failure of the IoT device) to a storage destination(e.g., storage manager 140, cloud storage 312, etc.) and then takingfurther action based on the transferred data such as troubleshooting anerror, generating an update to fix the error, and/or preserving the IoTdata in secondary copies 316. The process 500 can be initiated ortriggered by an error condition, an error flag issued by the IoT device,or by storage manager 140 based on a pre-established policy, etc. Eachcomputing device described in FIGS. 1-4 can execute the process 500. Insome implementations, the IoT data agent 314 (FIG. 3, FIG. 4B) executesthe process 500 to gather error information for an IoT device 302. Inother implementations, the client computing devices 102 (FIG. 3) the IoTmonitor 305, and/or system 100 perform all or at least part of theprocess 500.

At block 505, an IoT data agent 314 (from e.g., IoT monitor 305,information management system 100, and/or client computing device 102)establishes a connection with an IoT device 302. The IoT data agent 314can establish a connection with a device in several ways, includinguser-assisted setup, automatic detection of the IoT device on a network,or IoT device communication with a client computer or router. Foruser-assisted setup, a user can take a picture of an IoT device, inputIoT model or serial number information into a client computer using agraphical user interface, or use a mobile device to notify theinformation management system that the IoT device should be added to auser's network. In implementations where an IoT data agent automaticallyestablishes a connection with a device, the IoT data agent can becrawling or monitoring a network of devices, and if the IoT data agentdetects an IoT device, it can prompt a user to confirm that theinformation management system should be monitoring the device for erroror failure. The user can confirm this monitoring through a graphicaluser interface on a client device. In some implementations, the IoTdevice may include firmware or software that alerts the informationmanagement system that IoT device is on or now in use and should bemonitored for failure or errors.

In establishing a connection with the IoT device 302, the IoT data agent314 can enable a device (e.g., client computing device 102, IoT monitor305) to use various communication protocols. If the IoT data agentdetermines that the IoT device is Bluetooth® enabled, the IoT data agentcan use Bluetooth® to communicate with the IoT device. The IoT dataagent can determine if an IoT device is Bluetooth® enabled based onuser-provided information (e.g., serial number or model or device). Insome implementations, the IoT data agent is located on an IoT monitor,and the IoT monitor communicates with the IoT device in combination withthe IoT data agent.

At operation 510, the IoT data agent 314 generates a replica or snapshotof the IoT device memory, e.g., stored at IoT monitor 305. In someimplementations, the IoT data agent causes the IoT device to performreplication operations or snapshot operations to generate a replica ofthe data 303 of the IoT device. In some implementations, the IoT dataagent may request only a partial replica or partial amount of datarelated to a particular area of memory. In other implementations, theIoT data agent can request a complete block-level replica of the IoTdevice. To determine the size and type of replica, a user or techniciancan enable a policy (e.g., stored in management database 146 at storagemanager 140) based on type of IoT device or amount of space available tostore replicas. For example, a technician can enable a policy toreplicate the complete memory of an IoT smart plug because the IoT smartplug likely has a small amount (e.g., 1 gigabyte or less) of memory.Additionally, the replica may include only the structure of the memory,and not necessarily all the data. As a result, when the replica istransferred from the IoT device to a destination, e.g., cloud storage312, bandwidth can be preserved and network traffic is reduced.

At decision operation 515, the IoT data agent 314 determines whether atriggering event has occurred. A triggering event is a malfunction,error, or failure of the IoT device 302, or in some embodiments storagemanager 140 initiates a triggering event for purposes of gathering andprotecting IoT data 303. The triggering event is generally based on anerror alert or malfunction of the hardware or software on the IoTdevice, but the invention is not so limited. Some examples includereceiving an error code from the processor or receiving an indication ofan error stored in the memory. In other implementations, triggeringevents can be based on threshold conditions of the IoT device. Thresholdconditions are related to the suggested, maximum, or minimum operatingconditions of the IoT device. Some examples of threshold conditions aremaximum or minimum current or voltage, maximum or minimum temperature,suggested operating temperature, suggested operating power, and so on.The IoT data agent can determine these threshold conditions by findingthe technical specifications of the IoT device online or from the IoTdevice-related entity (e.g., IoT device manufacturer). The IoT dataagent can compare the threshold conditions and operating conditions(e.g., state conditions described in FIG. 4A) to determine if an erroror malfunction has occurred. If a triggering event has not occurred, theIoT data agent can continue to wait for an error to occur. If atriggering event has occurred, the process 500 moves to operation 520.

At operation 520, the IoT data agent 314 receives IoT device data 303(e.g., a log file) from the IoT device 302. The log file contains a logor logs related to the error, and in some implementations includesinformation such as state conditions related to the error. In someimplementations, the IoT data agent 314 is located in an informationmanagement system 100, and the storage manager 140 in the informationmanagement system determines where to store the IoT device data 303. Thestorage manager 140 can direct the creation of backup copies (e.g., 316)or deduplicate data log files if many IoT devices are experiencingerrors and sending log file data.

At operation 525, the IoT data agent sends the IoT device data 303(e.g., log files) to an electronic storage device 312 or to any storagedestination that is associated with information management system 100.If the IoT device data 303 is received by the information managementsystem 100, it can be copied or migrated to the electronic data storagedevices 315 (e.g., 315 a, 315 b, 315 c, etc.) within the system, ormigrated to a storage destination that is associated with theinformation management system 100, or between different locations in theinformation management system 100. The data can be stored either in anoriginal/native (e.g., data 303) and/or one or more different formats,e.g., suitable backup formats (e.g., data 316). For example, IoT datacan be transferred from one or more first storage devices to one or moresecond storage devices, such as from primary storage device(s) tosecondary storage device(s), from secondary storage device(s) todifferent secondary storage device(s), from secondary storage devices toprimary storage devices, or from primary storage device(s) to differentprimary storage device(s). The IoT data 303/316 can undergo backupoperations, archive operations, information lifecycle managementoperations such as hierarchical storage management operations,replication operations (e.g., continuous data replication operations),snapshot operations, deduplication or single-instancing operations,auxiliary copy operations, and the like. Some of these operationsinvolve the copying, migration or other movement of IoT data, withoutactually creating multiple, distinct copies.

Regardless of whether the IoT device data 303/316 is stored at the cloudstorage 312 or within the storage management system 100, or a storagedestination associated with the storage management system, the data303/316 can be made available for access by an IoT device-related entity(e.g., IoT manufacturer) that created or services the IoT device and/orthe data 303/316 can be backed up for storage. For example, a smartrefrigerator manufacturer can receive a log file associated with afailure of the refrigerator. The IoT device-related entity can then usethis log file to simulate the error, troubleshoot the error, or gathermore information about the error. If process 500 is repeated multipletimes for all smart refrigerators connected to a network, the entity cangain valuable data related to errors. The IoT device-related entity canthen categorize the errors or even develop solutions or fixes for theerrors.

At operation 530, a computing device receives a response from the IoTdevice-related entity. The operation at this block is optional, asillustrated by the dashed lines. As described in operation 525, the IoTdevice-related entity (e.g., IoT manufacturer or company that servicesthe IoT device) can develop an update or fix for the error. The IoTdevice-related entity can then send the fix or update to the IoT deviceto address the error. After operation 530, process 500 ends. In otherimplementations, process 500 can repeat.

Although process 500 uses log files as an example for information thatis sent from an IoT device, other types or information can be sentdepending on the IoT device or policy. Other types of informationinclude sensor data, minidump files, processor memory dumps and registerinformation, dynamically allocated memory, hard disk images, stateconditions, time stamps, data points, configuration files, messagequeues, API logs, or supervisory control and data acquisition data. Forexample, the IoT data agent can gather processor memory from the timeright before an error or during the error and send this information tothe database. Because the IoT data agent can gather differentinformation from different devices, it provides IoT device-relatedentities with flexibility when diagnosing or troubleshooting a problem.Additionally, the IoT data agent can also gather environment conditionsassociated with a failure or error such as sound level, temperature,light intensity, and humidity.

Alternatively, IoT device data 303 can be further integrated into ananalytics engine to provide analysis on usage patterns, performance,component degradation with time, and/or environmental effects. Portionsof the log files can be broken down into tokens such as type of error,component that generated the error, time etc. The tokenized data (e.g.,time vs. sensor in a key/value format) can be associated with the sensordata captured for further analysis. Alternatively or in addition, theIoT data can be backed up and stored by the information managementsystem 100 for archival, audit, and or to meet compliance requirements(e.g., legal holds).

Although decision operation 515 is based on triggering events, thedecision operation can also be based on a polling event or information.For example, an IoT data agent can poll IoT devices at a certainfrequency (e.g., every hour) to determine if the device has failed or isexperiencing an error. If the device has failed or is experiencing anerror, the IoT data agent can request state data from the device thatwas collected right before and/or after the error. If the device isoperating normally, the IoT data agent may not collect data from the IoTdevice and wait until the next polling period. Alternatively, IoT dataagent 314 can collect IoT data 303 regardless of whether an error orfailure is detected, for purposes of gathering and protecting the IoTdata at information management system 100.

Management of Internet of Things (IoT) Devices in Vehicles

Vehicles today have increasingly greater number of connected devicesonboard that can communicate with each other as well as through anetwork to navigate the vehicle, track maintenance and performance, andprovide in-vehicle entertainment. It is estimated that devices in anautonomous vehicle can generate about 30 to 60 terabytes of data perday. The data generated by some of these onboard IoT devices can be usedto analyze and predict equipment failures, track and locate the vehicle,improve vehicle safety, performance, and passenger experience. The datacan also be stored and used for regulatory, insurance, or legalrequirements. Disclosed herein are systems and methods for retrievingdata from IoT devices in vehicles for remote diagnosis, analysis,testing, updates, and storage.

Disclosed herein are systems and methods for protecting IoT (internet ofthings) device data connected to a vehicle. The system communicates withthe vehicle's IoT devices to collect data on the operation andperformance of those devices. The IoT devices may generate log filesthat may be collected and stored in databases as such time when the datacan be transmitted across a network to a destination storage environmentsuch as a cloud storage or an information management system. In someexemplary implementations of the disclosed technology, a thresholdnumber of log file entries are transferred as part of the log file basedon one of more of the following parameters: type of IoT device, vehicleassociated with the IoT device, age of IoT device, storage capacity ofIoT device, storage capacity of an IoT data agent, bandwidthconstraints, standard license agreement (SLA) requirements for fixingthe error (e.g., error is to be fixed within 5 minutes of detection,etc.), a predetermined number of log file data entries (e.g., 10 logfile data entries), size of the log file (e.g., maximum 10 MB), log filecreation time/date, etc. The disclosed technology can also determinewhich log files the IoT device created before and/or after a failure.After the disclosed technology gathers this information, it can storethe information in a database, or send it to a cloud provider or theinformation management system for diagnosis, analysis, testing, updates,and storage.

In some exemplary implementations of the disclosed technology, an IoTdata agent causes an IoT device in the vehicle to execute instructionsto transfer log files associated with an error from the IoT device tocloud storage to store the log files. For example, an IoT data agent canaccess an IoT device memory using Bluetooth® and install code on thedevice that enables the IoT device to send its log files to the cloudstorage if the device experiences an error or failure.

In other exemplary implementations, the IoT data agent can generate asnapshot or a replica of the IoT device memory. The replica can be ahard drive disk image of a part of the IoT device memory or the entirememory depending on policy standards set by a technician. Next, thedisclosed technology can store the snapshot or replica of the IoT devicememory in a database until failure or error occurs. If a failure orerror occurs on the IoT device, the disclosed technology can use an IoTdata agent to transfer relevant log file data from the IoT device to thedatabase storing the replica or snapshot of the IoT device. Techniciansthen can remotely view or run simulations using the snapshot or replicaof the IoT device, along with the log file data, without the need forphysical access to the IoT device directly. One advantage of thisdisclosed technology is that it aggregates valuable error or failureinformation for troubleshooting and replicates memories for IoT devices.

In other implementations, a computing device can poll IoT devices todetermine whether a failure or error has occurred. Polling includesquerying the IoT device at a certain frequency (e.g., hourly, daily) todetermine if an abnormal condition such as an error or failure hasoccurred. Abnormal conditions can be state values of the device thatindicate error or failure such as high current, high temperature,hardware error, or connectivity or sensor problems. The computing devicecan be an enhanced router (also referred to as an “IoT monitor”) thatuses Bluetooth® to communicate with IoT devices. In someimplementations, if the computing device polls an IoT device anddetermines that an error occurred, the computing device can send thestate conditions of the IoT device to a server or database for furtherprocessing and analysis.

FIG. 6A is a block diagram illustrating an environment 601 for gatheringIoT device data 603 from a vehicle. The environment 601 includes avehicle 604, comprising IoT device(s) 602 connected to the vehicle, IoTmonitor 605, a network 606, vehicle docking station 607, a computingdevice 608 comprising an IoT data agent 614, a cloud storage 612, and aninformation management system 100 comprising a storage manager 140 (FIG.1C), an IoT data agent 614, a media agent 144, and electronic datastorage device(s) 615. The blocks are schematic representations of thedevices in the environment 601, and each block is described below inmore detail.

The vehicle 604 can include a variety of IoT devices. The IoT devices602 can be sensors and/or controllers that sense temperature, weight,weather, distance, light, speed, positioning, etc. Some examples of IoTdevices include navigation devices (e.g., lidar/radar sensors, GlobalPositioning Devices (GPS), cameras, etc.) and in-car entertainmentdevices. The term vehicle is used herein to refer to any vehicle thatcan support an IoT device whether or not the vehicle relies on humaninput to operate or control the vehicle. Exemplary vehicles useful inthe present invention include electric and combustion type vehicles(e.g., cars, trucks, vans, and wagons, etc.). Electric vehicles caninclude semiautonomous and autonomous vehicles that can move or guidethemselves with limited human input or without human input as suchvehicles will typically contain IoT devices (e.g., IoT sensors,controllers, actuators etc.) to facilitate operation and/or control ofthe vehicle.

In the embodiment illustrated in environment 601, the vehicle 604 cancomprise one or a plurality of IoT devices 602. An IoT monitor 605 maybe connected to one or more of the IoT device(s) 602 in someembodiments. The IoT monitor 605 is a computing device that cancommunicate with the IoT device(s) 602 by connecting wirelessly orthrough wired connections with the IoT device(s) 602. The IoT monitor605 can also monitor the IoT device(s) 602, for example, to determinewhether the devices are on, off, or experiencing failure. The IoTmonitor 605 comprises or is associated with data 603 gathered from orabout IoT device(s) 602. In some embodiments, data 603 is a snapshot,copy, and/or replica of data generated by IoT device(s) 602 and capturedby IoT monitor 605. In some embodiments, data 603 additionally oralternatively comprises reporting or analytic information gatheredand/or reported by IoT monitor 605 in reference to one or more IoTdevices 602 that it is monitoring, e.g., an error report, a statusreport, etc., without limitation. The IoT monitor 605 can be installedby the vehicle manufacturer during assembly of the vehicle andintegrated into the vehicle's control system. The IoT monitor 605 canalso be a distinct physical component co-located within the vehicle'sother components or its functional constituent components can beintegrated into the vehicle's systems. Alternatively, the IoT monitorcan be placed with the docking station 607. An exemplary IoT monitor 605is further described in FIG. 7B.

The vehicle docking station 607 illustrated in FIG. 6A can be any devicethat facilitates the transfer of IoT device data 603 from the vehiclethrough a network 606 to a storage destination (e.g., cloud storage 612or electronic data storage device(s) 615). The docking station 607 cancomprise a combination of hardware and/or software that communicateswith the IoT devices either directly or indirectly through the IoTmonitor. An example of a docking station 607 can include an electricalvehicle charging station (e.g., in a public facility or privateresidence) or a petroleum-based fueling station that is connected to thenetwork 606. In one example, the vehicle docking station can have acommunication module that communicates with the IoT device or with theIoT monitor to facilitate transmission of the IoT device data 603 whilethe vehicle is parked at the docking station. Transmission of the IoTdevice data 603 to a storage destination may occur while the vehicle isbeing charged/fueled at the docking station 607 and/or when the vehicleis connected directly to the network without being parked at the dockingstation 607. Another example of a docking station 607 may also include avehicle diagnostic station or testing station (e.g., in a vehicle repairshop). The diagnostic or testing station can comprise a computer systemhaving processors, sensors, microchips to determine problems or issuesassociated with the operation or performance of the IoT device(s) in thevehicle, and in some embodiments such a diagnostic or testing stationcomprises IoT monitors 605 in addition to or instead of then IoTmonitors 605 in vehicle 604, without limitation.

A stand-alone computing device 608 comprising a processor, memory andcommunication module (not illustrated), and an IoT data agent 614 may beassociated with the vehicle docking station 607. Alternatively, thefunctional constituent components of the computing device 608 and theIoT data agent 614 can be integrated into the docking station 607. TheIoT data agent 614 analogous to the IoT data agent 142 described in FIG.1C, however, the IoT data agent 614 includes some additionalfunctionality to enable the transfer of information from the IoT devices602 to a storage destination (e.g., cloud storage 612 and electronicdata storage 615 associated with the information management system 100).More generally, the IoT data agent 614 performs information managementoperations related to the IoT devices by copying, archiving, migrating,and/or replicating the IoT device data 603 as directed by the storagemanager 140. In some implementations, the IoT data agent 614 can sendcomputer-executable instructions to the IoT monitor 605 that cause theIoT devices 602 to send log files, perform data dumps, perform backupoperations, or take snapshots of memory for these devices. In someimplementations, the functionality of the IoT data agent 614 can bedistributed across the IoT device(s) 602, the IoT monitor 605, thecomputing device 608 and/or the information management system 100,however, the location of the data agent and its functionalities is notso limited as the IoT data agent 614 functionalities may be concentratedat a single location (e.g., residing solely at the computing device 608)rather than having its functionalities distributed across multiplecomponents or devices. The environment 601 disclosed herein can executealgorithms that are described in more detail in the text correspondingwith FIG. 8.

As shown in FIG. 6A, the environment 601 includes a cloud storageenvironment 612 (e.g., a private cloud or one operated by a third-partycloud service provider) for storage of data from the IoT devices.Examples of third-party public cloud storage services include Amazon WebServices® or Microsoft^(Azure)®. The vehicle 604, the IoT monitor 605,IoT device(s) 602, vehicle docking station 607, the computing device608, and the information management system 100, can send IoT deviceinformation to the cloud storage environment 612 through the network 606using a network interface, such as by wired or wireless communication.Likewise, the cloud storage environment 612 can send information back tothe IoT devices through the network as shown by the bi-directionalarrows in FIG. 6A.

The network 606 can be the Internet or some other public or privatenetwork. The network may also include local area network (LAN), a widearea network (WAN), a cellular network, a computer network, or acombination of networks that connects the devices shown in FIG. 6A. Theunderlying physical communications infrastructure for network 606 andfor the other communicative connections depicted in FIG. 6A, whetherwired and/or wireless, is well known in the art.

The information management system 100 illustrated in FIG. 6A is similarto the information management system 100 described in FIG. 3, as itcomprises a storage manager 140 described in FIG. 1C, IoT data agent(s)614, media agent(s) 144, and electronic data storage device(s) 615(e.g., 615 a, 615 b, 615 c . . . 615 n). The storage manager 140 maycommunicate with, instruct, and/or control some or all elements of theinformation management system 100 including the IoT data agent(s) 614and the media agent(s) 144, as well as information management operationsthat are applied to IoT data 603, e.g., copying, archiving, etc.

The information management system 100 can store IoT device data 603 inthe form of backup copies (e.g., secondary copies 616 in the electronicdata storage devices 615) as illustrated in FIG. 6A. As illustrated inFIG. 6A, the electronic data storage device(s) 615 (e.g., 615 a, 615 b,615 c . . . 615 n) can generally be of any suitable type including,without limitation, disk drives, storage arrays (e.g., storage-areanetwork (SAN) and/or network-attached storage (NAS) technology),semiconductor memory (e.g., solid state storage devices), tapelibraries, or other magnetic, non-tape storage devices, optical mediastorage devices, combinations of the same, etc. In some embodiments,electronic data storage devices form part of a distributed file system.In some cases, electronic data storage devices are provided in a cloudstorage environment (e.g., a private cloud or one operated by athird-party vendor)(e.g., 615 b), whether for primary data or secondarycopies or both.

The storage manager 140 illustrated in FIG. 6A is similar to the storagemanager 140 described in FIG. 1C and FIG. 3. The storage manager 140 cancommunicate with, instruct, and/or control the IoT data agents 614 andthe media agent(s) 144 which are specialized programmed logic and/orhardware capable of writing to, reading from, instructing, communicatingwith, or otherwise interacting with electronic data storage devices 615.Such media agent(s) 144 can be utilized to make secondary copies of IoTdata (e.g., secondary copies 616) that can be stored in backup format,archive format, or other formats not native to the format of the primarydata 603.

The information management system 100 can also communicate with thecloud storage environment 612 to exchange data. IoT device data can betransmitted between the two systems to coordinate analysis and datastorage functions. In one exemplary embodiment, the cloud storage 612may be used by a device-related entity to store data for testing andanalysis of the IoT device data 603. For instance, the IoTdevice-related entity can use the data stored in the cloud storage 612to troubleshoot the IoT device failure and send a fix or software updateto the IoT device. The IoT device data can also be sent to the storagedestination (e.g., electronic data storage device 615) associated withthe information management system 100 for long term storage in order tocomply with legal discovery, regulatory or insurance requirements. Thisexample is only an illustration of one embodiment as the roles of thesetwo systems are not so limited and can be distributed between the twostorage systems. In another exemplary embodiment, the cloud storage 612may function as a long-term storage repository for the IoT device datawhile the electronic data storage devices 615 can be used for storagepurposes related to analytics and testing of the IoT device data.

FIG. 6B is an illustrative data flow diagram depicting movement of theIoT data 603 from one location to another location according to certainembodiments of this disclosure. In one embodiment, IoT data 603 may betransferred directly from the vehicle 604 using pathway 1 a and throughnetwork 606 for storage at the storage destination (e.g., cloud storage612 or in the storage devices 615 associated with the informationmanagement system 100) via pathways 2 a or 2 b. If the IoT data 603 isstored in the cloud storage 612, it may optionally be transferred usingpathway 3 a to the information management system 100 where it may becopied, deduplicated, or modified into a format that is different fromits original format (e.g., for storage purposes). Thereafter, the IoTdata (e.g., 616) can be transferred to one of the storage devices 615 inthe information management system using pathway 3 b. Likewise, if theIoT data 603 is received via pathway 2 b and first stored in theinformation management system 100, it may be optionally copied and/ortransferred to the cloud storage 612 using pathway 3 a.

In another embodiment illustrated in FIG. 6B, the IoT data 603 may betransferred from the vehicle through the docking station 607 usingpathway 1 b. The IoT data 603 can move through the network and can bestored in the storage destination using either pathways 2 a or 2 bdepending on how the data is intended to be stored or used. Likewise,the IoT data 603 can also be transferred from a computing deviceassociated with the docking station using pathway 1 c. The data can movethrough the network for storage in the storage destination using eitherpathway 2 a or 2 b. As illustrated by the double arrows, dataoriginating from the storage destinations (e.g., updates, repairs and/orinstructions) can also be transferred using pathways 2 a and 2 b throughthe network 606 to the IoT devices in the vehicle 604 either throughpathways 1 a, 1 b and/or 1 c.

FIG. 6C is an illustrative example of an IoT data agent 614 associatedwith the IoT device 602. The IoT data agent 614 can be executed on thesame IoT device it operates on. The IoT data agent 614 accesses the IoTdevice memory 704 to copy and transfer the IoT device data 603 (e.g. logfiles 705 and/or state data 707) or it can cause the IoT device totransfer the IoT data 603 through the network using pathway 1 a and tothe storage destination using either pathways 2 a and 2 b. Thisconfiguration can be utilized if the IoT device has insufficientprocessing power and/or storage capability to process or store largeamounts of IoT data as the IoT data 603 can be transferred over pathway1 a while the IoT data 603 is being generated by the IoT device.

FIG. 6D is another illustrative example where the IoT data agent 614executes on the docking station 607 (not illustrated) or a computingdevice 608 associated with the docking station 607 (as illustrated). IoTdata 603 can be collected by the IoT data agent 614 when the vehicle isconnected to the docking station 607. The data agent can cause the IoTdevice to transfer the IoT data 603 or connect directly to the IoTdevice 602 and copy the data from the device. The IoT data 603transmitted from the vehicle can be transferred over the network 606through pathway 1 b or 1 c and to the storage destination. Thisconfiguration may be utilized if the IoT device 602 has access tosufficient storage capacity to store the IoT data 603 until a connectionis made by the data agent 614 (associated with a docking station) to theIoT device 602 or its associated memory device.

FIG. 6E is another illustrative example of an IoT data agent 614associated with an IoT monitor 605 in communication with the IoT device.A triggering event monitored by the IoT monitor may cause the data agent614 to copy IoT data or cause the IoT device 602 to transfer data forstorage in the data storage module 705 illustrated in FIG. 7B. When thevehicle connects to a docking station 607, the IoT data can betransferred through the network to a storage destination.

FIGS. 7A and 7B are block diagrams illustrating more details for the IoTdevices 602 and the IoT monitor 605 previously shown in FIGS. 6A-6E. Inparticular, FIG. 7A illustrates an example of an IoT device 602 whichincludes a processor 702, memory 704, an input/output (I/O) module 703,and a communication module 710. The memory 704 can have log files 705,and/or a log agent 706, and/or state data 707 (dashed lines indicatethese are optional). The IoT device 602 can vary in size, processingpower, memory structure and type, and components, and can include all orsome of the optional components shown by dashed lines in FIG. 7A. Theoverall structure of the IoT device 602 generally varies based onfunction.

Continuing with FIG. 7A, the processor 702 can access the memory 704.The memory 704 can include hardware devices for volatile andnon-volatile storage and can include both read-only and writable memory.For example, the memory can comprise random access memory (RAM),registers, read-only memory (ROM), and writable non-volatile memory,such as flash memory and hard drives. The memory 704 stores programs,software, and data such as log files 705, a log agent 706, and statedata 707, each of which is described in more detail in the nextparagraph.

Log files 705 generally include IoT device identification, vehicleidentification, type of triggering event, time, operating conditions,usage patterns, performance or degradation, or operating history for theIoT device 602. Log files data varies based on the type of IoT device.Log file categories can include security logs (e.g., spam, malware, orvirus information), authentication logs pertaining tosuccessful/unsuccessful login attempts, general information logs, logsrelated to configuration of devices, firewall logs, and devicemanagement logs, failure logs, warning logs, error logs etc., withoutlimitation.

The log agent 706 is software that enables the IoT device 602 to shareits log files. In some implementations, the IoT device 602 may not havea log agent 706, but the IoT data agent 614 can send installationinstructions to the IoT device 602 to install the log agent 706. Statedata 707 can also include configuration data, settings, user options,time stamps, sensor or sensed data, or session identifiers related tothe IoT device 602, etc., without limitation.

The I/O module 703 enables the processor 702 to be electrically coupledto a network card, video card, audio card, USB, FireWire, or otherexternal device. Also, the communication module 710 includes acommunication device capable of communicating in a wireless or wiredfashion with a network node, e.g., in network 606. The communicationmodule 710 can communicate with another device or a server through anetwork using, for example, TCP/IP protocols. In some implementations,the communication module 710 includes hardware and software forBluetooth®, ZigBee®, ZigBee Remote Control®, Z-Wave®, 6LowPAN®, Thread®,Wi-Fi, cellular (3G, 4G, LTE and 5G etc.), Near Field Communication,SigFox®, Neul®, and LoRaWan®.

Although not illustrated in FIG. 7A, the IoT device 602 may have an IoTdata agent 614 (or specialized functional components thereof)pre-installed during manufacture of the device. Alternatively, the IoTdevice may download the IoT data agent 614 (or specialized functionalcomponents thereof) when the IoT device establishes a network connectionand then connects with a preprogrammed, installer programmed or userprogrammed address (e.g., URL) that the IoT device is to connect to uponpower up or periodically (e.g., weekly/monthly). The IoT data agent 614can be modified to have functions distributed across different devices.This can reduce the burden on the limited resource IoT device 602, whichmay have insufficient memory and/or processing ability to support allthe functioning requirements of the IoT data agent 614. For instance,the IoT data agent installed at the IoT device can have specializedfunctions only (e.g., making replicas and migrating the data), and theremainder of its functions can be distributed to one or a plurality ofother devices as previously discussed.

Moving to FIG. 7B, the IoT monitor(s) 605 is a combination of hardwareand/or software that monitors the IoT device(s) 602 to determine if acertain threshold value or triggering event has occurred. The IoTmonitor may also collect IoT data 603 for regulatory, insurance, orlegal purposes based on a pre-established storage policy, or for anypurpose or reason, without limitation. The IoT monitor(s) 605 eachinclude the processor 702, the memory 704, the I/O module 703, thecommunication module 710, an optional IoT data agent 614, and datastorage module 705 for storing IoT device data 603 obtained from one ormore IoT device(s). Although these components carry the same referencenumbers as components of the IoT device 602, they need not be physicallyidentical or identically configured, depending on the implementation.

The IoT monitor 605 enables bidirectional communications between IoTdevices 602 with the docking station 607 and/or the computing device 608as illustrated in FIG. 6. In another embodiment, the IoT monitor 605 mayalso enable bidirectional communications between IoT devices 602 and thestorage destination (e.g., cloud storage 612 and storage 615 associatedwith the information management system 100). The IoT monitor 605provides device-to-storage destination and storage destination-to devicecommunications including file transfer and request-reply methods to/fromstorage destination. The IoT monitor 605 can communicate with the IoTdevices 602 with no human operator. In some implementations, the IoTmonitor also provides security. For example, the IoT monitor canauthenticate (e.g., verify the identity) of each IoT device 602 and thevehicle in the network 606 shown in FIG. 6. In some implementations, theIoT monitor 605 includes libraries of IoT protocols such as MessageQueue Telemetry Transport (MQTT), TCP/IP, Hypertext Transfer Protocol(HTTP), Constrained Application Protocol (CoAP), or Advanced MessageQueueing protocol (AMQP). In other implementations, the IoT monitor 605can store or upload custom protocols or convert custom protocols intoe.g., MQTT, TCP/IP, HTTP, or AMQP.

The IoT monitor 605 monitors the IoT devices for triggering events(malfunctions, errors, failures etc.) and identifies the IoT devicehaving such triggering event. The IoT monitor 605 can also poll IoTdevice(s) at specific time periods (e.g., every hour) to determine ifthe device has experienced a triggering event. If the IoT device 602 hasfailed or is experiencing an error, for example, the IoT monitor 605 canrequest state data from the device that might have been collected rightbefore and/or after the error/failure event. If the device is operatingnormally, the IoT monitor may not collect data from the IoT device 602and wait until the next polling period. The IoT monitor 605 can receiveone or more of the following information from the IoT deviceexperiencing the triggering event: log file, minidump file, processormemory dump, register information, dynamically allocated memory; harddisk image, state conditions, time stamps, data points, configurationfiles, message queues, API logs, supervisory control data, oracquisition data, without limitation. The IoT monitor 605 can relay thisinformation to the IoT data agent 614.

FIG. 8 is an exemplary flow diagram for implementing a process 800 fortransferring IoT device data 603 from an IoT device 602 to a database orother data structure suitable for storing IoT data 603 (e.g., at cloudstorage 612 or electronic data storage device 615 associated with theinformation management system 100). The process 800 begins at block 805and continues to block 830. Process 800 generally includes establishinga connection with an IoT device, generating a copy of the IoT devicememory, transferring log files or other data related to the IoT device(e.g., data related to the failure of the IoT device) to a storagedestination and then taking further action based on the transferred datasuch as troubleshooting an error or generating an update to fix theerror, and/or preserving the IoT data 603 in secondary copies 616. Eachcomputing device described in FIG. 6 can execute the process 800,depending on how the components are configured and/or installed. In someimplementations, the IoT data agent(s) 614 executes the process 800 togather information from the IoT device(s) 602. In other implementations,the computing device 608, the IoT monitor 605, and/or the informationmanagement system 100, perform all or at least part of the process 800.

At block 805, IoT data agent(s) 614 establishes a connection with an IoTdevice 602. The IoT device(s) 602 may have the IoT data agent 614 (orfunctional components thereof) directly installed on the device atmanufacture as in embodiment disclosed in FIG. 6C. Alternatively, theIoT device(s) may also download the IoT data agent 614 when the IoTdevice establishes a network connection and then connects with apreprogrammed, installer programmed or user programmed address (e.g.,URL) that the IoT device is to connect to upon power up or periodically(e.g., weekly/monthly). The IoT data agent(s) 614 can also automaticallydetect the IoT device(s) 602 by crawling or monitoring a network ofdevices. The IoT data agent 614 can also connect to the IoT device(s)602 indirectly through the IoT monitor(s) 605 which are in communicationwith the IoT devices 602 as in the embodiment disclosed in FIG. 6D. Insome implementations, the IoT device 602 may include firmware orsoftware that alerts the IoT data agent 614 that the IoT device(s) is onor now in use and should be monitored for failure or errors. In someembodiments, data agent 614 connects to and obtains data 603 from IOTmonitor 605 and does not directly connect with IOT devices 602.

In establishing a connection with the IoT device(s) 602, the IoT dataagent 614 can enable a device (e.g., computing device 608, IoT monitor605) to use various communication protocols. If the IoT data agent 614determines that the IoT device is Bluetooth® enabled, the IoT data agentcan use Bluetooth® to communicate with the IoT device. The IoT dataagent 614 can determine if an IoT device is Bluetooth® enabled based onpreinstalled information (e.g., serial number or model or device). Insome implementations, the IoT data agent 614 is located on an IoTmonitor 605, and the IoT monitor 605 communicates with the IoT device602 in combination with the IoT data agent 614 as in the embodimentillustrated in FIG. 6D.

At operation 810, the IoT data agent 614 can generate data 603 (such asa replica or snapshot of the IoT device memory) that is stored at theIoT device 602 or stored at IoT monitor 605. In some implementations,the IoT data agent 614 causes the IoT device(s) 602 and/or monitor 605to perform replication operations or snapshot operations (described inFIG. 1C) to generate a copy of the data 603 on the IoT device(s) 602. Insome implementations, the IoT data agent 614 may request only a partialcopy or partial amount of data 603 related to a particular area ofmemory. In other implementations, the IoT data agent can request acomplete copy of the IoT device(s) 602. To determine the size and typeof copy, a pre-determined policy can be established by thedevice-related entity or technician based on the type of IoT device oramount of space available to store the copy. For example, a techniciancan enable a policy to copy the complete memory of an IoT device(s) 602because the IoT device(s) 602 may have a small amount (e.g., 1 gigabyteor less) of memory. Additionally, the copy may include only thestructure of the memory, and not necessarily all the data. As a result,when the copy is transferred from the IoT device(s) 602 to a database orsuitable structure for storing data, bandwidth can be preserved, andnetwork traffic is reduced. The copy of the device memory may be storedin the IoT monitor 605 for transmission to the destination storage.

At decision operation 815, the IoT data agent 614 determines whether atriggering event has occurred. A triggering event can be a predeterminedtime interval, a threshold condition, a malfunction, error, or failureof the IoT device 602, or in some embodiments, the storage manager 140initiates a triggering event for purposes of gathering and protectingIoT data 603. More than one triggering event may occur that may cause aspecific action. The triggering event is generally based on an erroralert or malfunction of the hardware or software on the IoT device, butthe invention is not so limited. More detailed examples of triggeringevent include receiving an error code from the processor or receiving anindication of an error stored in the memory. In other implementations,triggering events can be based on threshold conditions of the IoTdevice. Threshold conditions are related to the suggested, maximum, orminimum operating conditions of the IoT device. Some examples ofthreshold conditions are maximum or minimum current or voltage, maximumor minimum temperature, suggested operating temperature, suggestedoperating power, and so on. In another example, the triggering event canalso include reaching a threshold number of data files or a thresholdlimit on the size of the data. The IoT data agent 614 can determinethese threshold conditions by finding the technical specifications ofthe IoT device(s) 602 online or from the IoT device-related entity(e.g., IoT device manufacturer or developer). Such technicalspecifications can also be previously provided to the IoT data agent orduring the installation and association of the IoT data agent with theIoT device or with the IoT monitor. The IoT data agent 614 can comparethe threshold conditions and operating conditions (e.g., state datadescribed in FIG. 7A) to determine if an error or malfunction hasoccurred. A storage policy may determine the actions taken against aspecific triggering event. If a triggering event has not occurred, theIoT data agent can continue to wait until such occurrence. If atriggering event has occurred, the process 800 moves to operation 820.

Although decision operation 815 is based on triggering events, thedecision operation can also be based on a polling event. For example, anIoT data agent 614 associated with the IoT monitor 605 can poll IoTdevices at a certain frequency (e.g., every hour) to determine if thedevice has failed or is experiencing an error. If the device has failedor is experiencing an error, the IoT data agent can request state datafrom the device that was collected right before and/or after the error.If the device is operating normally, the data agent may not collect datafrom the IoT device or the data can be collected from the IoT device bythe IoT data agent 614 based on a preestablished storage policyregardless of whether an error or failure is detected. The collecteddata can be stored in the data storage module 705.

At operation 820, the IoT data agent 614 may receive IoT device data 603from the IoT device(s) 602 as in the exemplary configurations describedin FIGS. 6D and 6E. The IoT device data 603 may be stored in the IoTdevice memory 704 or the IoT monitor's data storage module 705. The IoTdevice data 603 can be logs or log files related to the error or thedata can be state conditions related to the error. In someimplementations, the IoT data agent 614 is located on a storagemanagement system 100, and the storage manager 140 determines where tostore the data. The storage manager 140 with the media agent 144 cancreate backup copies or deduplicate the data (e.g., data log files).

At operation 825, the IoT data agent 614 can send the IoT device data tothe storage destination (e.g., 612) for access by the IoT device-relatedentity (e.g., IoT manufacturer or company) if access to the network isavailable by the IoT device either through the communication protocolsavailable from the vehicle or the IoT monitor as in the exemplarypathways illustrated in FIG. 6B. In the direct pathway illustrated inFIG. 6C, the IoT data is sent directly from the vehicle to the storagedestination. This may avoid the necessity for the vehicle to park at adocking station to transfer the device data using the docking station'snetwork communication protocols Alternatively, the IoT device data 603can be transmitted using the docking station's communications protocolwhen the vehicle is docked as further discussed in more detail in FIGS.6D and 9. A determination on using the direct or indirect transmissionof IoT device data 603 may depend on the size of the data, the urgencyfor transmission, or the type of data. Alternatively, if the type ofdata contains sensitive data (privacy related data), transmission may bedelayed until the vehicle is docked and a more secure network connectionis established. Also, if the data is relatively large and/or intendedfor long-term storage, it may be stored by the IoT monitor until suchtime that the data can be transmitted (e.g., at the docking station withbroadband internet connections).

If the IoT device data 603 is received via pathway 2 b (FIG. 6B) by theinformation management system 100, it can be copied or migrated to theelectronic data storage devices 615 (e.g., 615 a, 615 b, 615 c, etc.)associated with the information management system 100 or betweendifferent locations within the information management system 100. Thedata can be stored either in an original/native (e.g., data 603) formatand/or in one or more different formats, e.g., suitable backup formats(e.g., data 616). For example, IoT data can be transferred from one ormore first storage devices to one or more second storage devices, suchas from primary storage device(s) to secondary storage device(s), fromsecondary storage device(s) to different secondary storage device(s),from secondary storage devices to primary storage devices, or fromprimary storage device(s) to different primary storage device(s). TheIoT primary data 603 and IoT secondary data 616 can undergo backupoperations, archive operations, information lifecycle managementoperations such as hierarchical storage management operations,replication operations (e.g., continuous data replication operations),snapshot operations, deduplication or single-instancing operations,auxiliary copy operations, and the like. Some of these operationsinvolve the copying, migration or other movement of IoT data 603/616,without actually creating multiple, distinct copies.

Regardless of whether the IoT device data 603/616 is stored at the cloudstorage 612 or storage associated with the storage management system100, the data 603/616 can be made available for access by an IoTdevice-related entity that created or services the IoT device and/or thedata 603/616 can be backed up for storage. The IoT device-related entitycan then use the IoT device data to simulate, test and/or troubleshootthe error, or gather more information about the error. Thedevice-related entity may also store the IoT device data (e.g., logs andmemory replicas) for compliance purposes. If process 800 is repeatedmultiple times for all similar IoT devices connected to differentvehicles, the device-related entity can gain valuable data related tooperation, safety, and or performance of the IoT devices. The IoTdevice-related entity can then categorize the errors or even developsolutions or fixes for the errors.

At operation 830, the computing device 608 can receive a response fromthe IoT device-related entity. The operation at this block is optional,as illustrated by the dashed lines. As described in operation 825, theIoT device-related entity can develop an update or fix for the error.The IoT device-related entity can then send the fix or update to the IoTdevice to address the error. After operation 830, process 800 ends. Inother implementations, process 800 can repeat.

FIG. 9 depicts some salient sub-operations of block 825 in process 800.

In general, block 900 is executed by the IoT data agent 614 andinformation management system 100 and is directed to transfer of IoTdevice data 603 from the IoT device to the storage destination when thevehicle is docked at the docking station 607.

At block 905 the vehicle comprising IoT devices connects to the dockingstation 607. A connection may occur when the vehicle is parked at thedocking station or when the vehicle is connected to a diagnostic ortesting device.

At block 910 the vehicle and/or its IoT devices is authenticated by theIoT data agent. The authentication step can include looking up thevehicle's identification number (VIN) or the IoT device identification(e.g., make and model number) against a pre-established database storedin local memory or stored in a memory location on a remote device.

At block 915, if the vehicle and/or IoT devices passes theauthentication process, the IoT data agent initiates copying of the IoTdevice data 603 directly from the IoT device memory 704, the IoT monitormemory 704, or data storage module 705 (See FIGS. 7A and 7B). Initiationof the data transfer can include the IoT data agent identifying all theavailable IoT devices associated with the vehicle and executing thestorage policy associated with each of the IoT device's data. Forinstance, the IoT data agent can selectively pull IoT device data fromcertain devices or pull data from either a point in time or from aparticular event. This allows for going back in time where data transferwas stopped because the vehicle was disconnected prior to completion ofdata transfer. The retrieved IoT device data 603 can be temporarilystored locally at the charging station or transferred directly to astorage destination. The IoT data agent can also receive IoT data fromthe cloud storage while the vehicle is docked for association andtransmission to the information management system or the data agent canreceive and transmit updates, repairs or fixes to the IoT devices asdiscussed further below.

At block 920, the IoT data agent may determine whether previously storedIoT device information should be retrieved from the storage destination.Such information may include previously stored fixes, updates, orrepairs to the IoT devices or data that was previously stored in thestorage destination (e.g., partial data that was previously uploaded toa storage destination requiring consolidation with current IoT data).For example, the IoT data agent can request co-relating location data ofthe IoT device logs which was previously stored in the cloud storage forretrieval and to consolidate such location data with the current logsfrom the vehicle's IoT devices in order to back it up to the informationmanagement system. The IoT data agent can also request partially uploaddata that because of time (vehicle was prematurely disconnected from thedocking station prior to full transfer of data), or size constraintscould not previously be completely transferred. Such data can beassociated together and transmitted to the information management system100.

If the IoT data agent 614 determines that previously stored informationis required, the IoT data agent 614, at block 925, sends a request tothe storage destination (e.g., cloud storage 612 or storage 615associated with the information management system 100) requesting theinformation. Although process 900 illustrates a linear process, theinvention is not so limited, as the determination step 920 and/orrequest for previously stored information step 925, can occurimmediately after the vehicle (and/or IoT devices) is authenticated orit may occur concurrently with receipt of IoT device data by the fromthe vehicle, step 915.

If the previously stored IoT device information was not found in thestorage destination or it is unnecessary to retrieve the information,then the IoT data agent 614 proceeds to block 930 for transmitting IoTdevice data 603 received from the IoT device 602 or from monitor 605 inthe vehicle to the designated storage destination. At block 930, the IoTdevice data 603 is either stored to the computing device's 608 memory ora memory module in the docking station 607 for later transmission or thedata is immediately transferred through the network to the storagedestination while the vehicle is docked. A pre-established storagepolicy can establish data transmission timing and priority. This can bebased on parameters such the size of the data, the estimated time thevehicle will be at the docking station, the device the data comes from,the priority level of the data, and the availability of the network totransmit the data etc.

At operation 940, the IoT data agent then transfers the received IoTdata to a storage destination, either the cloud storage 612 (e.g., foranalysis by the device-related entity) or the storage 615 associatedwith the information management system 100 where it can be stored andused for further analysis, testing, or for regulatory, legal, and/orcompliance purposes. The IoT data agent can also receive information(e.g., updates, fixes etc.) from the storage destination, as in step925, and transmit such information to the IoT devices in the dockedvehicle.

Although the processes described herein refers to log files as anexample of data that is sent from an IoT device, other types orinformation can be sent depending on the IoT device or storage policy.Such types of information include sensor data, minidump files, processormemory dumps and register information, dynamically allocated memory,hard disk images, state conditions, time stamps, data points,configuration files, message queues, API logs, or supervisory controland data acquisition data. For example, the IoT data agent can gatherprocessor memory from the time right before an error or during the errorand send this information to the storage destination. Because the IoTdata agent can gather different information from different devices, itprovides IoT device-related entities with flexibility when diagnosing ortroubleshooting a problem. Additionally, the IoT data agent can alsogather environmental conditions associated with a failure or error suchas sound level, temperature, light intensity, and humidity.

Alternatively, IoT device data 603 can be further integrated into ananalytics engine to provide analysis on usage patterns, performance,component degradation with time, and/or environmental effects. Portionsof the log files can be broken down into tokens such as type of error,component that generated the error, time, etc. The tokenized data (e.g.,time vs. sensor in a key/value format) can be associated with the sensordata captured for further analysis. Alternatively, or in addition to theactivity disclosed above, the IoT data can be backed up and stored bythe information management system 100 for archival, audit, and or tomeet compliance requirements (e.g., legal holds).

In regard to the figures described herein, other embodiments arepossible within the scope of the present invention, such that theabove-recited components, steps, blocks, operations, messages, requests,queries, and/or instructions are differently arranged, sequenced,sub-divided, organized, and/or combined. In some embodiments, adifferent component may initiate or execute a given operation.

EXAMPLE EMBODIMENTS

Some example enumerated embodiments of the present invention are recitedin this section in the form of methods, systems, and non-transitorycomputer-readable media, without limitation.

In some embodiments, a system for protecting IoT (internet of things)device data connected to a vehicle is disclosed. The system communicateswith the IoT devices to collect data on the operation and performance ofthe IoT devices that are connected to the vehicle. The system may becomposed of at least one IoT (internet of things) device having aprocessor and nonvolatile memory and an IoT monitor in communicationwith the at least one IoT device. The IoT devices may generate data(e.g., based on a triggering event) that may be collected and stored indatabases as such time when the data can be transmitted across a networkto a destination storage environment such as a cloud storage or aninformation management system. The system may or may not utilize anintermediate docking station to facilitate transmission of the data.More specifically, IoT data agents whose functionalities may bedistributed among the IoT devices, the IoT monitor, the docking stationor the information management performs the information managementoperations of the IoT device data such as copying, archiving, migratingand replicating.

In other embodiments, a computer-implemented method to manage data fromIoT devices connected to a vehicle is disclosed. The IoT devicegenerates IoT device data such as log files associated with theoperation of the IoT device in the vehicle. The method establishes by anIoT monitor connected to the IoT devices that a triggering event hasoccurred. The triggering event can be based on a predetermined storagepolicy, an error, a failure, or a malfunction of an IoT device connectedto the vehicle. The IoT monitor can poll the IoT devices for triggeringevents. An IoT data agent associated with the IoT device or IoT monitormay take a snapshot of the IoT device memory or a replica of the IoTdevice memory having the triggering event. The snapshot, replica, or logfiles (collectively included as IoT device data) may be stored by theIoT monitor until a connection is made by the vehicle with a dockingstation that is connected through a network to either a cloud storage oran information management system. The IoT device data may be transferredthrough the network to the cloud storage or the information managementsystem for analysis and testing, software fixes, for archiving to meetregulatory or compliance requirements, or integrated into an analyticsengine to provide further insight into the IoT device data.

In other embodiments, a computer-implement method to manage data fromIoT devices connected to a vehicle is further disclosed. The methodestablishes connecting a vehicle containing IoT devices that assist withthe operation or performance of the vehicle to a vehicle dockingstation. These IoT devices having a processor and non-volatile memorymay generate IoT device data related to the operation or functioning ofthe vehicle. Upon a triggering event, a portion or all of an IoT devicedata can be immediately captured and sent to a remote location such as acloud storage environment. When the vehicle is docked at the dockingstation, an IoT data agent can authenticate the vehicle and itscomponent IoT devices and determine that a triggering event has occurredwith the IoT devices. The IoT data agent can retrieve the previouslystored IoT device data from the cloud storage and associate thepreviously stored IoT device data with the IoT device data received fromthe vehicle. The associated data can then be sent to the informationmanagement system for storage, testing and analysis as previouslydescribed.

In some embodiments, a computer-implemented method to manage an Internetof Things (IoT) device is disclosed. The method establishes, by an IoTdata agent, a connection with an IoT device, wherein the IoT deviceincludes nonvolatile memory and generates a copy (e.g., replica orsnapshot) associated with the IoT device. The copy can include a copy ofat least a portion of the IoT device memory. The method determines, bythe IoT data agent, that a triggering event has occurred. The triggeringevent can at least partially relate to an error, a failure, or amalfunction of the IoT device. In response to determining that thetriggering event has occurred, the method receives a log file from theIoT device. The log file includes a threshold number of log data entriesfor the IoT device and includes log data entries for the IoT device upuntil the triggering event. The method sends the log file from the IoTdata agent to an IoT device-related entity. The IoT device-relatedentity can be an entity that created, troubleshoots or services the IoTdevice.

In some embodiments of the invention, a computer-implemented method tomanage an Internet of Things (IoT) device is disclosed. The methodcomprises monitoring, by an IoT data agent, a network of IoT devices.When an IoT device that is not currently connected to the IoT data agentis detected, the method prompts a user to confirm the connection to theIoT device. When the user confirms the connection, the methodestablishes, by the IoT data agent, the connection with the IoT device.The method then generates, by the IoT data agent, a replica of aspectsof the IoT device. The replica includes a copy of at least a portion ofmemory within the IoT device. The method polls the IoT device atpredetermined time intervals to identify an exception event. Theexception event at least partially relates to an error, a failure, or amalfunction of the IoT device. When an exception event is identified,the method receives information from the IoT device, including one ormore of the following: log file, minidump file, processor memory dump,register information, dynamically allocated memory, hard disk image,state conditions, time stamps, data points, configuration files, messagequeues, API logs, supervisory control data, or acquisition data. Themethod sends the received information from the IoT data agent to an IoTdevice-related entity. The IoT device-related entity can be an entitythat created, manufactured, troubleshoots, manages or services the IoTdevice.

In other embodiments, a system for performing a method of managing IoTdevices is disclosed. The system communicates with IoT devices to gatherinformation related to the IoT devices. The information can include dataabout device failure or error(s) even if the IoT devices are limited inresources. For example, the information includes log files that containat least some information related to the device's failure. The systemcan store this information in a database, send it to the IoTdevice-related entity, or send it to a storage environment provided by acloud provider. The IoT device-related entity can then use thisinformation to troubleshoot the failure and send a fix or softwareupdate to the IoT device.

In other embodiments, a system for performing a method of managing IoTdevices is disclosed. The system causes one or more IoT devices toexecute instructions to transfer information (e.g., log files, statusmessages, etc.) to a storage manager. Depending on the location of theIoT device, an IoT data agent at the system can communicate with the IoTdevice via a specific communication protocol (e.g., short-range,medium-range, long-range, etc.). Based on the information transferred tothe storage manager, the system can troubleshoot one or more errors orfailures of IoT devices.

In other embodiments, a system or systems may operate according to oneor more of the methods and/or computer-readable media recited in thepreceding paragraphs. In yet other embodiments, a method or methods mayoperate according to one or more of the systems and/or computer-readablemedia recited in the preceding paragraphs. In yet more embodiments, acomputer-readable medium or media, excluding transitory propagatingsignals, may cause one or more computing devices having one or moreprocessors and non-transitory computer-readable memory to operateaccording to one or more of the systems and/or methods recited in thepreceding paragraphs.

Terminology

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense, i.e., in the sense of “including, but notlimited to.” As used herein, the terms “connected,” “coupled,” or anyvariant thereof means any connection or coupling, either direct orindirect, between two or more elements; the coupling or connectionbetween the elements can be physical, logical, or a combination thereof.Additionally, the words “herein,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. Where thecontext permits, words using the singular or plural number may alsoinclude the plural or singular number respectively. The word “or” inreference to a list of two or more items, covers all of the followinginterpretations of the word: any one of the items in the list, all ofthe items in the list, and any combination of the items in the list.Likewise the term “and/or” in reference to a list of two or more items,covers all of the following interpretations of the word: any one of theitems in the list, all of the items in the list, and any combination ofthe items in the list.

In some embodiments, certain operations, acts, events, or functions ofany of the algorithms described herein can be performed in a differentsequence, can be added, merged, or left out altogether (e.g., not allare necessary for the practice of the algorithms). In certainembodiments, operations, acts, functions, or events can be performedconcurrently, e.g., through multi-threaded processing, interruptprocessing, or multiple processors or processor cores or on otherparallel architectures, rather than sequentially.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described. Software and other modules mayreside and execute on servers, workstations, personal computers,computerized tablets, PDAs, and other computing devices suitable for thepurposes described herein. Software and other modules may be accessiblevia local computer memory, via a network, via a browser, or via othermeans suitable for the purposes described herein. Data structuresdescribed herein may comprise computer files, variables, programmingarrays, programming structures, or any electronic information storageschemes or methods, or any combinations thereof, suitable for thepurposes described herein. User interface elements described herein maycomprise elements from graphical user interfaces, interactive voiceresponse, command line interfaces, and other suitable interfaces.

Further, processing of the various components of the illustrated systemscan be distributed across multiple machines, networks, and othercomputing resources. Two or more components of a system can be combinedinto fewer components. Various components of the illustrated systems canbe implemented in one or more virtual machines, rather than in dedicatedcomputer hardware systems and/or computing devices. Likewise, the datarepositories shown can represent physical and/or logical data storage,including, e.g., storage area networks or other distributed storagesystems. Moreover, in some embodiments the connections between thecomponents shown represent possible paths of data flow, rather thanactual connections between hardware. While some examples of possibleconnections are shown, any of the subset of the components shown cancommunicate with any other subset of components in variousimplementations.

Embodiments are also described above with reference to flow chartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products. Each block of the flow chart illustrationsand/or block diagrams, and combinations of blocks in the flow chartillustrations and/or block diagrams, may be implemented by computerprogram instructions. Such instructions may be provided to a processorof a general purpose computer, special purpose computer,specially-equipped computer (e.g., comprising a high-performancedatabase server, a graphics subsystem, etc.) or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor(s) of the computer or other programmabledata processing apparatus, create means for implementing the actsspecified in the flow chart and/or block diagram block or blocks. Thesecomputer program instructions may also be stored in a non-transitorycomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to operate in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the acts specified in the flow chart and/or blockdiagram block or blocks. The computer program instructions may also beloaded to a computing device or other programmable data processingapparatus to cause operations to be performed on the computing device orother programmable apparatus to produce a computer implemented processsuch that the instructions which execute on the computing device orother programmable apparatus provide steps for implementing the actsspecified in the flow chart and/or block diagram block or blocks.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the invention can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further implementations of theinvention. These and other changes can be made to the invention in lightof the above Detailed Description. While the above description describescertain examples of the invention, and describes the best modecontemplated, no matter how detailed the above appears in text, theinvention can be practiced in many ways. Details of the system may varyconsiderably in its specific implementation, while still beingencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the invention with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the invention to the specific examplesdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe invention encompasses not only the disclosed examples, but also allequivalent ways of practicing or implementing the invention under theclaims.

To reduce the number of claims, certain aspects of the invention arepresented below in certain claim forms, but the applicant contemplatesother aspects of the invention in any number of claim forms. Forexample, while only one aspect of the invention is recited as ameans-plus-function claim under 35 U.S.C. sec. 112(f) (AIA), otheraspects may likewise be embodied as a means-plus-function claim, or inother forms, such as being embodied in a computer-readable medium. Anyclaims intended to be treated under 35 U.S.C. § 112(f) will begin withthe words “means for,” but use of the term “for” in any other context isnot intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly,the applicant reserves the right to pursue additional claims afterfiling this application, in either this application or in a continuingapplication.

I/We claim:
 1. A method for managing log files for an IoT deviceconnected to a vehicle comprising: determining by an IoT monitor that atriggering event has occurred, wherein the triggering event comprisesone of: an error, a failure, and a malfunction of an IoT deviceconnected to an autonomous vehicle, and wherein the IoT device generatesat least one log file associated with the operation of the IoT device inthe autonomous vehicle; taking at least one of a snapshot of an IoTdevice memory and a replica of the IoT device memory of the IoT devicehaving the triggering event; storing by the IoT monitor, at least aportion of the at least one of: the snapshot of the IoT device memory,the replica of the IoT device memory, and the at least one log file ofthe IoT device; connecting the autonomous vehicle comprising the IoTdevice and IoT monitor with a vehicle docking station connected througha network to one of: a cloud storage and an information managementsystem, and wherein the information management system comprises astorage manager, a media agent, and a data storage device; transferringthe at least one of the snapshot of the IoT device memory, the replicaof the IoT device memory, and the at least one log file of the IoTdevice through the network to the at least one of a cloud storage and aninformation management system.
 2. The method of claim 1, wherein thedocking station comprises an IoT data agent and receiving by the IoTdata agent previously stored data related to the IoT device, from acloud storage environment before transferring the at least one of thesnapshot the IoT device memory, the replica of the IoT device memory,and the at least one log file of the IoT device through the network tothe information management system.
 3. The method of claim 2, wherein thepreviously stored data related to the IoT device from the cloud storageenvironment is associated by the IoT data agent with the at least onelog file.
 4. The method of claim 1, wherein the IoT monitor polls theIoT device for a triggering event.
 5. The method of claim 1, wherein thetriggering event occurs when an operating condition of the IoT device isoutside a range of a threshold condition and the threshold condition isone of: current, voltage, temperature, and power.
 6. The method of claim1, wherein the vehicle docking station comprises one or more of: anelectric charging station, a petroleum-based fueling station, adiagnostic station, and a testing station.
 7. The method of claim 1,wherein the at least one of: the snapshot of the IoT device memory, thereplica of the IoT device memory, and the at least one log file of theIoT device is stored as a secondary copy in the information managementsystem.
 8. The method of claim 1, wherein the at least one of thesnapshot of the IoT device memory, the replica of the IoT device memory,and the at least one log file of the IoT device, is sent to the cloudstorage and wherein the information management system communicates withthe cloud storage to initiate backup of the at least one of the snapshotof the IoT device memory, the replica of the IoT device memory, and theat least one log file to the information management system.
 9. Themethod of claim 1, further comprising tokenizing the at least one IoTlog file into a unit data format by the information management system.10. The method of claim 1, wherein the IoT monitor further comprises aprocessor, non-volatile memory, data storage module, input/outputmodule, and communication module.
 11. The method of claim 1, wherein atleast one of: the IoT monitor, the IoT device, the vehicle dockingstation, and the information management system comprises an IoT dataagent.
 12. A method for managing log files for an IoT device connectedto a vehicle comprising: connecting a vehicle to a vehicle dockingstation, wherein the vehicle comprises an IoT device and an IoT monitor,in association with the vehicle, and wherein the IoT monitor is incommunication with the IoT device, and wherein the IoT device comprisesa processor and non-volatile memory, and wherein the IoT devicegenerates at least one log file, and wherein the vehicle docking stationcomprising an IoT data agent is connected to a cloud storage and to aninformation management system through a network; and authenticating bythe IoT data agent, the vehicle and the IoT device; determining by theIoT data agent that a triggering event has occurred with the IoT device,wherein the triggering event comprises at least one of: a malfunction,an error, or a failure of the IoT device; determining by the IoT dataagent that previously stored data relating to the IoT device is storedin the cloud storage; receiving by the IoT data agent, IoT log filesgenerated by the IoT device in the vehicle; receiving by the IoT dataagent, the previously stored data relating to the IoT device from thecloud storage; associating the IoT log files with the previously storedIoT device related data; and transferring by the IoT data agent the IoTlog files received from the vehicle and previously stored data relatingto the IoT device received from the cloud storage, to the informationmanagement system.
 13. The method of claim 12, further comprisinggenerating by the IoT data agent at least a portion of one of: a replicaof the IoT device memory and a snapshot of the IoT device memory. 14.The method of claim 12, wherein the IoT log files comprise at least oneof: IoT device identifier, vehicle identifier associated with the IoTdevice, age of the IoT device, storage capacity of the IoT device, andlog file creation time and data.
 15. The method of claim 12, wherein thetriggering event occurs when an operating condition of the IoT device isoutside a range of a threshold condition and the threshold condition isone of: current, voltage, temperature, and power.
 16. The method ofclaim 12, further comprising tokenizing the IoT log files into unit dataformat by the information management system.
 17. The method of claim 12,wherein the previously stored data related to the IoT device comprisespartial log files.
 18. The method of claim 12, wherein the informationmanagement system comprises a storage manager, media agent, and datastorage device.
 19. The method of claim 12, wherein at least one of: theIoT device, the IoT monitor, and the storage management system, furthercomprises an IoT data agent.
 20. The method of claim 12, wherein thepreviously stored IoT device related data and the IoT log files receivedfrom the vehicle is backed up to a secondary storage in the informationmanagement system.